So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
UnZoner said:
So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
Click to expand...
Click to collapse
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
lewmur said:
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
Click to expand...
Click to collapse
This is what I was afraid of. It is my sons tablet so I have all his Google info. I would not be surprised if he somehow reset the developer options. He'll lose some of his game progress but that's nothing compared to losing the whole tablet. Thanks for the reply. Off to download a stock rom and start over.
Related
so your phone doesnt boot and you have the s6 edge plus logo flashing your face with some red text in the upper corner saying fap lock something something
first things first. your phone does charge while in download mode, so get your ass into download mode by holding the power button, menu and down at the same time
1. plug your phone to charging stuff while you wait
figured that out my self after accedentally disabling the oem thingy and restarting with about 10% left of battery
what you absolutly need to do is to calm down and head over to sammobile and
2. get the correct stock rom for your phone
3. after downloading you need to unzip the file and flash it through the ap section of the odin software, once thats done you are good to go, the phone should start up as usual and you will have all your apps and stuff waiting for you, just with stock rom, stock bootloader and stock recovery, after that you should head over to the developer section and enable oem unlock
when thats done feel free to flash a custom recovery, rom etc...
just remember, never ever ever ever ever disable the oem unlock in developer mode if you have a custom binary
you could also use the smart switch software from samsung, fiy the serial number is on the back on your phone and is pritty hard to read and your model number can be found in the download mode
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Did you hold the power button down until your phone completely powered off? I'm assuming you did. What you described isn't supposed to happen on a dual partition phone. If an update goes bad the phone is supposed to recover by booting from the other partition. If powering the phone down completely and then turning it back on doesn't allow you to boot I would honestly go straight to Essential Support since you didn't mod your phone or unlock the bootloader. I dealt with support via email and if nothing else they are definitely very responsive. They answer emails so promptly it was almost like being in a chat.
devon4786 said:
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Click to expand...
Click to collapse
Hello
Tell us the status of your phone Did you solve the problem? Tell us the way I'm stuck in the same problem
i factory reset my device and now it says "official released binaries only " in red and it wont boot at all. idk what to do.. i dont know how to force it to go into download mode i tried plugging it into the computer but it doesn't help. it just keeps restarting over and over again i only see the Samsung S10+ with the Yellow Triangle logo with that message at the top then it reboots. " anyone got any ideas how i can fix this there isn't a samsung store near me. if i plug-in the device into the computer it just keeps rebooting to the samsung s10 screen with the yellow triangle saying at the top in red "Only Official released binaries are allowed to be flashed" my issue is that i can't get the phone into download mode i tried holding down Bixby volume down power then plugin the usb cable. and even bixby volume up and power . it just keeps rebooting itself (sm-G975F)
have a quick look at this thread..... you should be able to boot into download mode, make sure u have the drivers for your phone installed on your pc. you will need to flash another firmware via odin (id recommend stock firmware to get you back on track )
https://forum.xda-developers.com/galaxy-note-9/help/official-released-binaries-allowed-to-t3893592
100000x likes.. you saved me bro.
volume down + bixby that was the magic key's to get back into download mode. i am flashing the firmware now. thank you again. i couldn't figure it out and i was going nuts .
? glad to help
meddylad said:
? glad to help
Click to expand...
Click to collapse
i lost oem unlock so i changed the date to may 1st and it showed up. but now how do i get it back to grayed out.. because when it needs internet it changes the date back to. todays date. got any ideas.
edit: when i reset up the phone after i checked oem unlock i put the the date for 10 days ago. so that the unlock stayed. anyways thanks again @meddylad
I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight
meddylad said:
I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight
Click to expand...
Click to collapse
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?
rp4k said:
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?
Click to expand...
Click to collapse
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.
Visera said:
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.
Click to expand...
Click to collapse
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.
rp4k said:
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.
Click to expand...
Click to collapse
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.
Visera said:
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.
Click to expand...
Click to collapse
Well this trick works fine on the s10.
Hi, something like a year ago I rooted my phone, something like half an year ago I installed LineageOS 14.1 and succesfully rooted it with Magisk.
I used it without any problems since today: I used it this mroning, then I shut it down so that it could charge (the battery is getting old, it doesn't charge enough if it's running)
Then I turned it on, but it didn't turn on because the FRP lock suddenly turned on. ...that means, as the splash screen prompted up, the "custom binary blocked by FRP lock" message
showed up. I couldn't enter TWRP recovery, but I could go in download mode, so I decided to flash a stock rom grabbed from the internet (I used Odin).
The stock rom is not working, it gets reboots as a message saying "installing applications...." shows up.
I don't care about the system itself, I only want to get my data stuck in it, so wiping data and cache is not an option.
EDIT: I tried using 2 different stock roms, and both seem to reboot after a fixed amount of time, like 3-4 seconds. I can enter the stock recovery and download mode.
I have same problem. Installed from stock rom to viperos. Cann't boot to back os, shows only frp lock..and then shut down. Please, could some one tell me how to fix it? I don't want to back stock rom. Thank you.
vgran said:
I have same problem. Installed from stock rom to viperos. Cann't boot to back os, shows only frp lock..and then shut down. Please, could some one tell me how to fix it? I don't want to back stock rom. Thank you.
Click to expand...
Click to collapse
Hi, I gave up trying to find a solution so I simply did a factory reset (by loosing all my data).
But if you flash the stock rom, you shouldn't lose data, but you can get access to the stock recovery mode. From there, you can use the adb shell to do "things".
I personally wanted to use the shell to retrieve data from my phone, but by flashing the stock rom the "usb debugging" option got disabled, so I couldn't do anything with that adb shell.
I advise you to try finding a way to enable usb debugging using the stock adb shell only (the shell wich is in "sideload" mode), I didn't find one but I didn't search a lot on that because I've already spent hours on trying to find a solution for the frp lock.
By searching I mean something like that: "enable oem unlock/usb debugging from adb in sideload mode"
(of course if you can't access the recovery mode and you don't have a backup)
So I've been trying to flash Ivan_Meler's LineageOS 19 zip with NikGApps Stock on my Galaxy S8+, and the setup went smoothly, however, when I restart the phone I am greeted with the "Galaxy S8 Powered by Android" splash screen along with red text at the top saying "Custom binary blocked by FRP Lock". The phone then powers off. When I turn the phone on, the same message appears, then turns the phone off. I can't access the system or the recovery, so I did some research, only to find that the only way was to reflash stock firmware through download mode, so I did.
I tried doing some more research, but I didn't find any resources on how to prevent this error from occurring in the first place (other than signing out of Google and deleting any screen locks on the stock firmware, which I already did). I've tried flashing the same rom three times, all with the same result.
Another detail I noticed: When I reboot the phone during the setup before I sign into my Google account, it works fine. Unfortunately, I need to sign into my Google account for personal use, so skipping signing in is not an option here.
What I'm asking is - is there any way to flash a custom rom with a Google account without that "Custom binary blocked by FRP Lock" error appearing on reboot?
Edit 1: I've done some more digging and it seems a possible reason for this error is that the OEM Unlock option has been disabled somehow. I will try tomorrow to verify that the OEM Unlock has been turned on after flashing.
Edit 2: Well the OEM Unlock option isn't there in the LineageOS developer tools. Figures since they probably assume your bootloader is already unlocked. I also tried using Zillinium's FRP Destroyer, but to no avail.
Edit 3: SOLUTION: Turns out using BitGApps instead of NikGApps Stock solves the problem.
Hy, I have got the same problem.
Which is the mistake?
Thanks for all