[Solved] Accidentally disabled OEM, "Custom binary blocked by FRP lock" on boot
Hi, so I was setting up a new game that refused to startup. A little bit of research and I found I needed to disable developer options to start it because of some protections it had. I did that and after it still didn't work I decided to restart my phone. Being an idiot, I completely forgot that I need developer options, specifically OEM Unlock enabled, for my phone to startup. I've looked up the issue a bit and it seems like I need to reinstall the stock ROM to fix this, but I'm not sure. So as for my main question, Is there a way for me to fix this, ideally without loosing data, root, xposed framework, Twrp recovery, all that? Also what will I lose/have to redo if that is not possible? I'm at class right now so I won't be able to try anything for a couple hours but I will as soon as I can.
Odin mode information as I can still boot into that (can't boot into Twrp it seems like)
Product name: SM-G920P
Current Binary: Custom
Current Status: Custom
FRP Lock: On
EDIT: Alright so I did more research once I got home and solved the issue using this thread. I literally just did this soo I havn't played around with it much but the important things are that I was able too keep all of my data, including app data. The only thing I know I lost was root (not sure about xposed or TWRP yet), but that's a small price to pay for getting this issue sorted.
Related
Hi,
after reading some information about the FRP, a perhaps possible way to bypass it on Samsung devices came into my mind:
After all, the only thing one has to do is somehow managing to open the settings app. From there, one can do a factory reset which will erase the FRP partition. There are already lots of ways to do so, mostly by exploiting "holes" in the UI.
And of course, the FRP is never really secure; as it relies on the inaccessibility of the phone's internal storage. So if one is able to write the flash by some means (for example JTAG), getting rid of the FRP is pretty much straightforward.
This to be said, just to assure you that I don't plan anything malicious. I'm just curious about Samsung's and Android's security measures, and I don't own any recent Samsung device (with FRP) to try it myself.
But now my thoughts: If FRP is active, from what I read one could not boot unsigned binaries flashed by Odin. But Odin seems to flash these images; it appears that it just blocks the boot.
The next point that flashing+booting modified firmware without triggering the Knox flag is possible. From what I read, the kernel and recovery must stay stock. Apps can change. So I assume that it behaves similar with FRP.
This brought me to an idea: Maybe one could modify a stock image so that one could get to a settings screen, flash it via Odin, boot it, open settings, do the factory reset, and do whatever you want form there.
As a modification, I would suggest just deleting the Gapps from the image; then the phone will never ask for a google account. Or put in one of the apps commonly used to bypass FRP by USB OTG.
The key question is: Will the device boot the modified image, or will one get the "Custom binary blocked by FRP" error?
i have been searching for hours and trying different methods and none seem to be working..
i am trying to root a samsung s6 g920i. it is updated to android 7.0
i have dev options enabled, debugging. the one thing i do not see on the device is OEM unlocking option.
so far ive tried odin3, i selected the cfar_samsung_sm-g920i_zerofltedv_nrd90m.g920idvs4frc9_t0 file, and it shows me successful messages in the odin3 results. but on the device it restarts real quick. once it restarts, its like nothing happened. the device is still rooted and there is no super user app.
ive followed numerous videos and threads all over and cant seem to get this device rooted.
is the oem unlocking option not showing up my issue? also, i noticed when the odin was doing its thing and the phone was restarting, there was a msg showing on the top left that stated "recovery is not seandroid enforcing" then the phone would restart.
any help here would be appreciated. it also looks like all of my samsung devices do not have the oem unlocking option under developer area (3 devices) so i am not sure what happened or what am i suppose to do.
Long Shot, but .....
Similar issues with a G9200 (Hong Kong version, dual SIM). You COULD try downloading Samsung's CROM.APK from the Play Store and see if you can unlock the bootloader that way. Are you by chance running recent Nougat on the device? My suspicion is that the Nougat kernel has been tweaked to disable the known rooting / custom recovery approaches. Areal pain in the butt. My next step with the 9200 is to see if erasing the NAND via Odin will allow me to flash an older MM build (I don't care about the data) root it, TWRP it, and put a decent ROM in place of stock.
Hello, how are you? My S8+ G955FD won't boot past the SAMSUNG logo. I am able to access the menu with the Power+Bixby+Vol+, but I don't know which option to use. I selected all of them twice.
The phone is not rooted and the bootloader has never been changed from it's original configuration. While trying to find a solution the question regarding the bootloader was sometimes asked. I don't know if it's locked or not, just that it has never been changed. The current and original OS is a carrier unlocked version. I have never enabled developer settings.
I know this question has been asked before, but I was just too overwhelmed by the number of results and couldn't find the guide for the S8+. I definitely found guides for other models and other brands of phones. I just need a working phone, it doesn't matter if it has root permissions or if the OS is version 1. I can forego the data, and will be happy with any kind of OS. The non-carrier specific would be best, my provider is Docomo. Please, how can I get my phone to boot properly again?
In an attempt to fix this I read through a some guides to flash the OS, most of them require that developer settings and usb debugging be enabled and I have never done that, nor do I know how to enable those without accessing the settings since the phone won't boot. So I didn't do anything beyond reading the directions and I feel stuck. What information can I provide that will help you walk me through to the solution? Thank you and may you have a wonderful day!
Try MXO pie via odin in Sammimobile
Hi All
I have an S7 Exynos with latest Magisk installed and everything has been working flawlessly till I decided this early morning, for not any particular reason(except my increasing amount of grey hair ), to lock the "developer options". I think I have done the same maybe a couple of years ago though cannot remember how I had solved it.
Obviously my phone was instantly locked.
Would someone be able to link a good working solution with being able to keep data and apps? I am a bit desperate as my work is starting again tomorrow.
Thanks a lot.
look at frp bypass
Costum binary blocked by FRP lock is a protection, whene you do a factory reset from recovery. the only way you get this message is with odin.
this one works for me on s7, s7 edge and s6 tab
Thanks @Dagobert
I will have a look at it now and see if it is not too scary. See my S7 FRP
kiwigi said:
deleted as repeated post
Click to expand...
Click to collapse
Do you have acces to the phone?
kiwigi said:
deleted as repeated post
Click to expand...
Click to collapse
If you have acces to the phone then backup your data do a factory reset. Then you can flash whatever you want. Frp lock is a google protection with a google account. Whene you do a factory reset from settings you wipe the frp.
What is Google FRP?
FAQ for Samsung Mobile Device. Find more about 'What is Google FRP?' with Samsung Support.
www.samsung.com
I have access to the phone via PC/Odin only. No booting as per image above. I wand to keep Data and Apps
I assume I have to flash stock with home csc to be able to enter the phone again? Then root again, if I so wish?
Yup. Maybee a long shot but try Flashing your former firmware with Odin, using HOME_CSC. I think thats the solution
More info on that in this topic
Help! How to flash without losing data?
Good day! My phone got stuck on breathing Samsung logo after my phone updates. Now the only option I have in mind is to restore factory data. But I have some important files in my phone that is very essential in my work. I know I have read that...
forum.xda-developers.com
hmm., done the flashing with the files plus home csc and it asks for password, which I have entered without success. I know the password and it justs does not accept it.
See the factory reset warning and the FRP lock still being on now.
I'm desperately trying to avoid wipping data and apps.
edit: unfortunately I had to format/reinstall as I could not find a workable option.
Good Morning Everyone
As the title suggests, i am looking to return my S22 Ultra back to stock.
i was on beyond rom for a bit, but too many apps complaining that my device was rooted has forced my hand to return my device back to stock once again.
I flashed the stock rom via odin, then locked my bootloader and wiped all data.
However i am still getting messages that my device is modifed.
Anyone got any ideas how to can truely return to full stock?
Thanks in advanced.
And yes i did do a search on the internet before asking, but i have been unable to find any advice outside of what i have already done.
happend to me, too. But only on the latest firmware. When I flash an older firmware, it won't appear. But after updating again to the latest ROM the message appears
Cheers mate. I'll give that a go.
Also note that if the device was rooted then you triggered the Knox flag and that one CANNOT BE RESET, it's an "efuse" (a hardware component that once changed it's state can only be reset by replacing it, i believe you need to replace the entire motherboard for that).
So, if the application checks the Knox status it will fail.
Here are a few apps that i know that will not work anymore :
- Knox itself (and any app that uses the Knox library/API )
- Samsung Pay
- Samsung Health
- Secure Folder
A few years ago I also had a banking app that failed to worked with a Knox flag triggered (on a Note 8), but after an update it allowed me to use the phone as long as i didn't have it rooted.