Database Users

S7 Edge - Custom Binary block by FRP Lock

Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!

Flash the stock firmware with ODIN
Envoyé de mon SM-G935F en utilisant Tapatalk

Thanks for the reply,
Sorry but I'm new. How do i do that?

pr0cupid said:
Thanks for the reply,
Sorry but I'm new. How do i do that?
Click to expand...
Click to collapse
What model? Country
Sent from my Blackberry Bold

Model : SM-G935FD
Country : Singapore

frp lock s7 edge
pr0cupid said:
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Click to expand...
Click to collapse
i have same issue here, did you find any solutions ?

AFAIK when you factory reset your phone etc. if rooted you must remember to go back into Developer Options and re enable OEM Unlocking. This depends on the method you used to root, if you flashed dm-verity then you "May not" have this issue but cannot say for sure.
If it is already too late for you then I think you need to flash stock via Odin, plenty of threads out there on where to find the firmware (SamMobile) and how to do it. Even a quick google of the error gave me plenty of results...
One thing I have read is that you may have to keep trying to get your phone into download mode as the timing is much stricter with this error message.

I've the same problem with my g935x blocked on FRP when ii treid to root if any one can help .plz

https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.

djluisbento said:
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
Click to expand...
Click to collapse
@djluisbento This method seems to be interesting. But would you please clarify more about it. How to install the apk file on official recovery? Or it's enough to have the pendrive connected? And if yes, when this step should take place, after flashing the official ROM or when?
I'm stuck in a boot loop into recovery mode with dm-verity error, and unfortunately I have the FRP locked, so I can't install TWRP to flash the no-dm-verity.zip file to skip it.
Appreciate your suggestions.

I have the same issure. stock firmware wont install either. im just stuck on the FRP screen, cant even get into recovery

Same issue here, please help
Everything was fine with rooting and installing TWRP. after that did a restart/ attempt to goto twrp recovery, from then the s7 edge is stuck at "Custom Binary Blocked By FRP" and doesnt boot. please help!!

Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
just quoting from the original thread by jcadduono.

Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.

maxkento said:
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
just quoting from the original thread by jcadduono.
Click to expand...
Click to collapse
taiseer999 said:
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
Click to expand...
Click to collapse
Yes, flashed both Zips in recovery. I used my regular google account during the initial set up. If i wait for 72 hours, will the phone just boot back online just fine? Still, how do i make sure it wont goto the FRP lock again while trying to reboot or reboot to TWRP?

Solved,
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.

anoopgopalpt said:
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
Click to expand...
Click to collapse
Helo
But U did this after 72 hours?

There are several methods depending on firmware version installed on your phone. Basically you have to enter in your phone, launch chrome, install an app which gives you the possibility to log into your google account from chrome and not set-up program.
I used successfully the Bluetooth method. Search for with google. You need a bluetooth headset and follow the steps described on youtube.
BTW. My phone was brand new and I flashed different official samsung firmware ( csc). I had to change google password in between and that resulted in FRP lock....
The wait time is 24 hours as is stated in google docs from site
Sent from my SM-G935F using XDA-Developers mobile app

Hello I have a related problem, opened a new thread, but my thread was closed, because my problem is related to this one, but more complicated. I have the same problem with FRP lock as described here, I can turn on the download mode but it wont be recognized by my computer. I tried different usb cables, drivers, even computers, it wont help. I cant flash it with odin, smartswitch, kies, no matter what I try. If I go to recovery mode it says `dm-verity verification failed...`and if I choose `apply update from ADB or SD card` it says `update from external storage disabled`. I dont know what to do anymore Its a new phone

FRP Block - no Dev Tools enabled
Hey guys,
you're my last resort, I've tried everything I happened to come across, to no avail.
First off, I did something incredibly stupid, don't even ask me why, as I have no idea what the heck drove me to do this in the first place.
Anyways, I was using the stock ROM on my S7 Edge, not tweaked or tinkered with besides the usual CF-Auto_Root. It never caused any trouble whatsoever. But for no reason at all this morning I decided to disable USB debuggin and OEM unlock. A short while later I rebooted my phone, which ended up in "Custom binary blocked by FRP Lock".
I gave a factory reset a try, but that obviously didn't change a thing. So I went to sammobile.com and downloaded the latest official stock ROM for my device and tried flashing it with Odin. Unfortnately Odin always fails with "Complete(Write) operation failed.", which I assume is because I messed with the settings in dev mode.
Next stop: ADB. I've never used that thing before, but I thought I should possibly be able to get it done following a simple guide. Unfortunately ADB won't even list my device when typing "adb devices". It's just an empty list.
So please guys, give me some tipps on how I can bring my phone back to life.

Please help me with my S7 Edge SM-G935F

Hello everyone,
My brother has just offered me a s7 edge SM-G935F / 32G, Rom stock without operator that he used for 2 months after purchase.
My pb is that after resertting this phone, then reboot, I am asked the google account with which this phone was syncing (it's of my bro). Normal!
Then I enter the data account google of my brother and then Passwords ... and there, a verification code sent him that communicates me by sms after receiving.
But helas, every time I get it, the phenomenon is repeated and so I can not use the phone for use!
My idea was to flash the last ROM Stock...but no way, the pb is always the same...the warning message !
For info, the dl and recovery mode are operational but I am without root so without TWRP and other ++++
However, the dev mode of the system is not activated too ...
Thank you for your help...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
B
sorry for my bad english !:silly:

Bishopandme said:
Hello everyone,
My brother has just offered me a s7 edge SM-G935F / 32G, Rom stock without operator that he used for 2 months after purchase.
My pb is that after resertting this phone, then reboot, I am asked the google account with which this phone was syncing (it's of my bro). Normal!
Then I enter the data account google of my brother and then Passwords ... and there, a verification code sent him that communicates me by sms after receiving.
But helas, every time I get it, the phenomenon is repeated and so I can not use the phone for use!
My idea was to flash the last ROM Stock...but no way, the pb is always the same...the warning message !
For info, the dl and recovery mode are operational but I am without root so without TWRP and other ++++
However, the dev mode of the system is not activated too ...
Thank you for your help...
B
sorry for my bad english !:silly:
Click to expand...
Click to collapse
You are facing FRP issue which is factory reset protection security feature by google..So everytime you will reset your device, you will be askd for the same google account which was previously added to device..Are you on marshmallow or nougat? IF your phone is functioning well then enable developers option by pressing build no for 7-8 times from software info you will find in about device from settings..After enabling developers option enable Oem unlocking..Hope this will help you..You can also flash latest stock firmware for your device usinh odin after enabling Oem unlocking from developers option

@DroidHackeR,
I'm in nougat because i have flash the latest Rom Stock yet with odin (4 files) + factory restet!
But the pb is the same...because i can't enable Oem unlocking from developers option by pressing build no for 7-8 times from software info
I have no access to do that, My procedure stops until the moment to put the login of gmail ... I do not go beyond that after the flash !
Another idea pl?
How can i enable Oem option directly by odin for example?
I can't flash custom rom because of it too...
Ths for your help.
B

Bishopandme said:
@DroidHackeR,
I'm in nougat because i have flash the latest Rom Stock yet with odin (4 files) + factory restet!
But the pb is the same...because i can't enable Oem unlocking from developers option by pressing build no for 7-8 times from software info
I have no access to do that, My procedure stops until the moment to put the login of gmail ... I do not go beyond that after the flash !
Another idea pl?
How can i enable Oem option directly by odin for example?
I can't flash custom rom because of it too...
Ths for your help.
B
Click to expand...
Click to collapse
Just download latest 7.0 stock firmware for your device from sammobile.com though your already on nougat..firmwares there are updated according to security patches timely..so my suggestion is download latest nougat firmware for your model and country and flash usinh odin as described above..You will boot normally...If after flashing latest nougat if your device stuck at Samsung logo i.e. called bootloop..Press volume up+power +home button, you will boot into stock recovery..from there choose wipe data/factory reset option..you will boot up normally..
---------- Post added at 02:48 PM ---------- Previous post was at 02:40 PM ----------
Bishopandme said:
@DroidHackeR,
I'm in nougat because i have flash the latest Rom Stock yet with odin (4 files) + factory restet!
But the pb is the same...because i can't enable Oem unlocking from developers option by pressing build no for 7-8 times from software info
I have no access to do that, My procedure stops until the moment to put the login of gmail ... I do not go beyond that after the flash !
Another idea pl?
How can i enable Oem option directly by odin for example?
I can't flash custom rom because of it too...
Ths for your help.
B
Click to expand...
Click to collapse
You can also refer this video by root junky which will give you option to overcome frp
https://m.youtube.com/watch?v=JzywoFS_r9U&time_continue=2

Ah ok...just after the reboot i doesn't let the phone start and must to reboot in recovery mode for doing the wipes and reset option.
ok i will do it as soon as...
wait for a moment pl!
B

@DroidHackeR,
i have just test your first idea and...it dosen't work !
I will test the video way ...it's seem no easy to me!
Ths for your help.
B

Bishopandme said:
@DroidHackeR,
i have just test your first idea and...it dosen't work !
I will test the video way ...it's seem no easy to me!
Ths for your help.
B
Click to expand...
Click to collapse
Go ti video reference and follow the steps carefully hope it will help you..Or another tricks are there to overcomd FRP issue i.e. using adb commands and otg cable..You can search on google.

DroidHackeR said:
Go ti video reference and follow the steps carefully hope it will help you..Or another tricks are there to overcomd FRP issue i.e. using adb commands and otg cable..You can search on google.
Click to expand...
Click to collapse
when i read the differents backs experiences...there's apparently a pb with the camera step way!
They said "On Samsung Galaxy s6 Edge plus there is no camera when you restart the phone. What's the Problem?"
and others phones too....
:crying:

i find this....for S7 Edge
https://www.youtube.com/watch?v=ChC...id=video:3e542a13-8bf9-4684-b336-004044a96320
tic tac

Bishopandme said:
i find this....for S7 Edge
&feature=iv&src_vid=JzywoFS_r9U&annotation_id=video%3A3e542a13-8bf9-4684-b336-004044a96320
tic tac
Click to expand...
Click to collapse
Yes refer this video to overcome FRP...Watch the video carefully and follow the steps described

Hi @DroidHackeR,
I realize that this video is no longer current because dating several months ... besides, nothing makes clear if this manupulations was made under Nougat or old versions ...
Recent updates may have blocked it, hence the large number of errors identified ...
what do you think?
Thank you !
B

Bishopandme said:
Hi @DroidHackeR,
I realize that this video is no longer current because dating several months ... besides, nothing makes clear if this manupulations was made under Nougat or old versions ...
Recent updates may have blocked it, hence the large number of errors identified ...
what do you think?
Thank you !
B
Click to expand...
Click to collapse
Will you please checkout the video i am going to provide link below? It claims about bypass of google FRP protection on devices running Nougat..i.e.s7edge is also included..Please watch this video carefully and report if it helped you or not
http://pangu.in/nougat-remove-google-verify-account-samsung-frp/

@DroidHackeR, OUrahhhh!!!!
Successfully with this method, look here: ....https://www.youtube.com/watch?v=8g4MG0ZRF1M&t=67s
Ths for all !
Enjoy !
B

Bishopandme said:
@DroidHackeR, OUrahhhh!!!!
Successfully with this method, look here: ....
&t=67s
Ths for all !
Enjoy !
B
Click to expand...
Click to collapse
Ohhhk dear @Bishopandme i am very glad to see your phone is saved and all of our quotes and comments are reserved in this thread to help any other suffering from same issue..Cheers..

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!

Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?

Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.

JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.

https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965

JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.

Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.

https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.

I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.

zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.

JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously

Good luck.

Deleted

Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.

JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...

sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.

sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!

I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you

Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082

Remove OEM Block on Samsung Galaxy J7 Pro / Unbrick

I want to share this with you since it was a real pain to figure this out.
I wanted to flash TWRP in order to flash custom roms into my phone. Mine is a J730G.
When I tried to flash twrp, I got the oem block event on the download mode, i could not get past it in any way. The instructions on how to flash twrp said to enable unblock OEM on developer options, but that option was not there when I looked for it. I knew that was what was not letting me.
After searching and searching and reading and trying every method I found, trying to enable OEM unblock option... I ended up soft bricking my device. I had the screen that said "an error has occurred while updating the device software". This was after trying the magicbox method. Don't do it.
So I had a bricked phone, was not able to flash twrp, and couldn't remove the damn oem block.
I found here on XDA that I could download the original firmware and flash it via odin and it should let me. So I downloaded the android 7.0 version original rom and it wouldn't let me flash it via odin, samsung doesnt want downgrades.... So I downloaded a 8.0 Vietnamese version I found here on xda uploaded on google drive. THANK YOU FOR UPLOADING IT! I am not able to post the link here since my account is new...but maybe you can let me know how to share it..
I downloaded that, flashed it via odin, and it worked! My phone was back. I just had to change the language and I was ok. But all this was to unblock OEM, so it was not over. I followed these steps I found in the beginning of my research. Make sure you flash the firmware without the sim card in just to make sure!! So after you flash:
1 On first boot up, skip everything, even wifi.
2 Go to date settings, change the date to 32 days back.
4 Go to update settings, turn off auto updates.
3 Reboot
4 Set up wifi. Don't let the phone download too many things.
5 Check for an update manually. Phone may have set auto date again after wifi was turned on... but its ok.
6 Reboot
7 Check for manual update again. You should have 1 pending update, DO NOT DOWNLOAD IT
8 Enable developer options
9 Go to developer options
10 OEM Unblock option will be there!!
11 ENABLE THAT MF!!
And that's it! You can now flash TWRP using odin. And from there you can do whatever you want!!
Hope this can help you and hope this method works for a while. Please let me know how to tag this post for it to be easy to find for others. I would like the owner of Prometheus Rom, ananjaser1211, to know about this! It could help his users manage to flash TWRP.
Thank you and good luck!

just copy and paste and remove the http://www part

OEM can't be unlocked

So, hi everyone I'm new but i think this is where I can post this. I'm helping a friend that did a lot of things to his J5 prime, here is what he told me:
"Ok so what I did is test a lot of Roms, evolution X, RR remix, octaviOS, nevapureOS, cynedragon, and some more, those ones are not in .zip, those are generic, so I needed to change the vendor and kebab, after I tried those, I changed to Android 12, then after testing on it for a bit, I tried changing it to try other ones, but when I tried to boot, it was looped, like, only the TWRP logo appeared, and nothing more, and so I tried to flash the stock ROM, but it didn't work, it said "Binary 9", so I tried with a binary 9 ROM (android 8). So I flashed the stock ROM, and I needed to wait until it unlocks the "Safe Mode", I waited something around a month, and the switch didn't appear, I also tried to go into the TWRP from ADB boot, it goes to a strange version of the download mode, like, the download logo appears, but the words that normally are in the top-left corner, are gone, and Soo, that's where I let the phone".
We tried flashing the TWRP, but, when we tried this appears: (img 1 & 2)
Please help, in like, one week he needs to give the phone to his sister and it would be bad for him to give the phone in that state (She knows about that stuff and we'll, she will check for sure).
Thanks Beforehand.

I've searched and found a thing called "Triangle Away", some say that it can downgrade binaries (which I've found is the problem of this)

Make sure developer mode and usb debugging is disabled.
--This new method worked for me and about 4 other guys with G570M--
Step 1: Wait for 168 hours
Step 2: Go to Date/Time settings and change the date to 05/05/2021.
Step 3: Restart and go to recovery and clear the cache
Step 4: When you turn on the device, make sure wifi is enabled and connected to some network, go to the update tab and disable auto update
Step 5: Click several times on the manual update button
Step 6: Go to developer settings and the oem should be there
---Wait for 168 hours with stockrom TTT---
Download Samsung Galaxy J5 Prime SM-G570M TTT Trinidad and Tobago G570MUBS9CTG3 firmware
Fast download latest Samsung Galaxy J5 Prime firmware SM-G570M from Trinidad and Tobago with G570MUBS9CTG3 and Android version 8.0.0
www.sammobile.com

I believe there is a trick to fool the device.
Remove SIM and perform a factory reset.
During setup, do not connect to a WiFi network.
Skip through setup and set time manually. Don't bother adding any accounts.
Once setup is complete, enable Developer Options.
Go into Date/TIme settings and set the date for 1 week minimum from today.
Go back into Developer Options and check if OEM Unlocking is available. If not, give it a few minutes and check again.