So guys, bought this phone used 3 days ago. The phone was rooted and the fingerprint scanner was not working giving some error. So I decided to get the phone returned back to stock.
I flashed the G925TUVU3DOJ7_G925TTMB3DOJ7_G925TUVU3DOJ7_HOME.tar file via odin 3.10.6. All files were successfully flashed with pass message but now i am stuck on the boot screen at s6 edge logo. I did a factory reset and wiped the cache but no luck.
The recovery shows an error of dm-verity verification failed... as well in the bottom. I can get the phone in download mode. The current binary is samsung official but in system status it still says Custom. I tried flashing G925TUVU2COF6_G925TTMB2COF6_G925TUVU2COF6_HOME.tar but it doesn't let me flash it as I read i cannot downgrade.
I have tried searching at different places but couldn't seem to find any appropriate solution as most of them are for cof6 or cof8 firmware. I would appreciate a lot if someone could guide me step-by-step procedure to get my phone working back.
Note: I think that the phone IMEI was also repaired as the IMEI on back glass and in the system does not match.
I also cannot get any assistance from t-mobile as I live in Pakistan. I could not attach shots as i have less than 10 posts so writing the status:
In download mode:
PRODUCT NAME: SM-G925T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0301)
AP SWREV: B:3 K:2 S:2
Recovery error at the bottom:
dm-verity verification failed. . .
Need to check DRK first. . .
It sounds like there may be an issue with your IMEI. I think you should try and use Smart Switch on your PC to do an emergency recovery. It will completely wipe the phone and reset everything to how it should be.
Emergency recovery requires the serial number in order to proceed. You can get that by going into Download mode but before you hit Vol Up to continue hit Home instead. It will show IMEI and Serial Number (the bottom number).
Samsung Smart Switch for PC can be downloaded from Here. Install Smart Switch. Start up Smart Switch and click more in upper right corner. If you don't have the Samsung drivers installed you can install them from here. Or if you would like to reinstall them.
After you are done with drivers connect your phone to the PC and click more and click "Emergency software recovery and initialization" (the first option). It should ask for your serial number. enter it and it should start doing it's thing.
Hopefully this works for you and good luck.
Thanks for the fast reply. I flashed it using the smart switch software. The program completed successfully but still the same result. Stuck at boot logo and same dm-verity error in recovery
DM Verity Verification failed
muhsaad said:
Thanks for the fast reply. I flashed it using the smart switch software. The program completed successfully but still the same result. Stuck at boot logo and same dm-verity error in recovery
Click to expand...
Click to collapse
Hello , if you still facing this issue after flash full stock
try to write unikernel v8-002 (remember FRP LOCK = OFF )
It must work ,
i am sure after flash Unikernel is will work
post result if not work
Thanks alot @jayshaa. Finally booted up... Hats off to you man...!! :good:
Sorry to disturb again... Today when I restart the phone, I couldn't pass the boot screen as I gave me the error Custom Binary blocked by FRP Lock. Frp lock turned on automatically and now I am again stuck at the boot screen. I again flashed the stock rom but the frp lock is still on. I couldn't flash the kernal as well because of this lock.
Someone please guide me to turn this frp lock off and get my phone working again.
Need to check DRK first. .
This error means at some point your efs probably was wiped meaning the drk was wiped... unless this is fixed the phone will boot loop everytime you update unless you flash a modified kernel...
So how do I fix that or turn frp lock off?
Anyone???
muhsaad said:
Sorry to disturb again... Today when I restart the phone, I couldn't pass the boot screen as I gave me the error Custom Binary blocked by FRP Lock. Frp lock turned on automatically and now I am again stuck at the boot screen. I again flashed the stock rom but the frp lock is still on. I couldn't flash the kernal as well because of this lock.
Someone please guide me to turn this frp lock off and get my phone working again.
Click to expand...
Click to collapse
That can only be turned off via Developer Options in Settings. If you flashed a custom kernel then you cannot turn it off because you will boot loop. You must flash stock kernel. Or just reflash the stock firmware package.
After you get back to stock. get to developer options and turn off the FRP lock. Then you can flash away.
Related
Hello friends, I have a big problem, I had my S6 edge with root in version 5.0.2, and wanted to upgrade to version 5.1.1, is the download version of SamMobile.
When the install had no error with ODIN, but when I start not pass "Samsung S6 edge powered by Android" To me this was strange to me, so I wanted to regain root, put it on, and start the cell as it should do, but when you restart to be installed on "kernel", the phone will not start, the left turned on the screen, but now with a message in red "(boot) blocked by FAP lock".
Then I went to put the original Samsung software (downloaded from SamMobile) and the same thing happened again, he would not turn on the phone, and to this day has not on, any solution would appreciate it pretty please
pablo5530 said:
Hello friends, I have a big problem, I had my S6 edge with root in version 5.0.2, and wanted to upgrade to version 5.1.1, is the download version of SamMobile.
When the install had no error with ODIN, but when I start not pass "Samsung S6 edge powered by Android" To me this was strange to me, so I wanted to regain root, put it on, and start the cell as it should do, but when you restart to be installed on "kernel", the phone will not start, the left turned on the screen, but now with a message in red "(boot) blocked by FAP lock".
Then I went to put the original Samsung software (downloaded from SamMobile) and the same thing happened again, he would not turn on the phone, and to this day has not on, any solution would appreciate it pretty please
Click to expand...
Click to collapse
Looks like you didn't disable the activation lock and unlock bootloader in developer options before attempting root. After you odin the 5.1.1 have you tried booting it into stock recovery immediately after? Try wiping the phone in there factory reset.
steve97ta said:
Looks like you didn't disable the activation lock and unlock bootloader in developer options before attempting root. After you odin the 5.1.1 have you tried booting it into stock recovery immediately after? Try wiping the phone in there factory reset.
Click to expand...
Click to collapse
hi bro, i do not remember if deselect, I think not clear, but I can not see if this down or not, because the phone does not turn on, and try to reboot in recovery mod wipe data /factory reset, and dropped it back software, but it has not worked /: ....
As the phone natzy would say "No phone for you" ?.
If you odined 5.1.1 you may be Sol, some users that did the official ota update have recovered from this by flashing stock firmware, but those that updated to 5.1.1 using Odin have not had any luck recovering from FRP lock.
Pp.
PanchoPlanet said:
As the phone natzy would say "No phone for you" .
If you odined 5.1.1 you may be Sol, some users that did the official ota update have recovered from this by flashing stock firmware, but those that updated to 5.1.1 using Odin have not had any luck recovering from FRP lock.
Pp.
Click to expand...
Click to collapse
it's ruined
Hello all,
I rooted my G925T device 1-2 weeks ago (SUPERSu?) and haven't had any major problems. Yesterday my phone died and while charging, I turned it back on only to get stuck on the T-mobile screen. I tried most everything including using Odin to reset to stock 5.1.1 firmware but I am getting a FAILED response (can't open the serial(com) port).
Some notes (not sure if relevant):
-90% sure my SuperSU was not enabled when my phone died and this started happening
-Pretty sure I unchecked the USB Debugging right after I rooted
-I wiped all my data from the recovery mode
Any help, tips, suggestions? THANKS!
bodef said:
Hello all,
I rooted my G925T device 1-2 weeks ago (SUPERSu?) and haven't had any major problems. Yesterday my phone died and while charging, I turned it back on only to get stuck on the T-mobile screen. I tried most everything including using Odin to reset to stock 5.1.1 firmware but I am getting a FAILED response (can't open the serial(com) port).
Some notes (not sure if relevant):
-90% sure my SuperSU was not enabled when my phone died and this started happening
-Pretty sure I unchecked the USB Debugging right after I rooted
-I wiped all my data from the recovery mode
Any help, tips, suggestions? THANKS!
Click to expand...
Click to collapse
Try this. Smart Switch usually can fix your boot loops. Be warned though you will lose everything on the phone. It will be reset to like you got it from the store. Except with the latest firmware.
can be deleted
jmc302005 said:
Try this. Smart Switch usually can fix your boot loops. Be warned though you will lose everything on the phone. It will be reset to like you got it from the store. Except with the latest firmware.
Click to expand...
Click to collapse
Hey, thanks for the reply.
Problem is, when I am in download mode it only tells me the following:
ODIN MODE (in red)
Product Name: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled (in blue)
KNOX WARRANT VOID: 1
RP SWREV: Letter:Number Letter:Number Letter:Number
And then Downloading... Do not turn off target
Flash Latest Stock ROM
bodef said:
Hey, thanks for the reply.
Problem is, when I am in download mode it only tells me the following:
ODIN MODE (in red)
Product Name: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled (in blue)
KNOX WARRANT VOID: 1
RP SWREV: Letter:Number Letter:Number Letter:Number
And then Downloading... Do not turn off target
Click to expand...
Click to collapse
FIrst Flash Full Stock Firmware than See if work .
1.If not work flash Unikernel V8-002 in odin.. ( it must work )
2.If both not work download firmware in 4 parts ...(BL,AP,CP,& CSC)
Just Flash only BL and AP (it work 100% Tested )
These must work ..
try and post result
The Emergency Recovery Smart Switch method worked!
I was able to find my s/n when I selected to view the barcode before going into download mode.
I thought s/n would be IMEI but its not.
bodef said:
The Emergency Recovery Smart Switch method worked!
I was able to find my s/n when I selected to view the barcode before going into download mode.
I thought s/n would be IMEI but its not.
Click to expand...
Click to collapse
I was just about to tell you that you need to press Home button to see S/N before you press Vol-Up. Glad you got it worked out. Please hit the thanks button if I helped you out.
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
NoirX said:
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
Click to expand...
Click to collapse
Probably going to have to wait 7 days
*Detection* said:
Probably going to have to wait 7 days
Click to expand...
Click to collapse
I tried that too but i think the issue is a little bit more complicated. The toggle is there but it does nothing. On stock firmware it goes through a factory reset as expected but the device remains oem locked. On combination firmware the toggle is there too, but it won't switch on. Thank you.
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
*Detection* said:
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
Click to expand...
Click to collapse
I'll try with normal Odin next time. I do suspect this might have been the issue.
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
bulky68 said:
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
Click to expand...
Click to collapse
Just realised that I got the 2 posters mixed up in my previous post. My apologies @*Detection* and @AMDPOWERFIST.
Hi,
I'm stuck on 'samsung' logo screen after flashing stock rom. Please see details below if you can assist.
1. I have sm-505fn from carphone warehouse uk with jan/feb 2020 update..
2. I did oem unlock and flashed twrp
3. this gave bootloader warnings, but eventually went into twrp.
4. I didn't do the dm verify installation and after couldn't get into twrp again. (not sure how to sideload this at this stage)
because i didn't do above step and rebooted, i think i tripped the knox and SG/RMM state became 'prenormal'.
kept getting error: "Only official released binaries are allowed to be flashed" if i tried installing twrp again.
5. tried installing stock rom btu for march 2019, but odin gave errors as couldn't install older stock.
6. then installed feb 2020 stock from sammobile rom A505FNXXS4ATB1 which is the btu version.
7. above worked fine with odin and everything succeeded.
8. On reboot the first warning vanished, and I only got the 2nd bootloader warning. phone went through a 5 second update screen, then rebooted.
9. then got samsung a50 logo and system started booting with plain samsung logo.
10. been stuck at plain samsung logo for 40 min. tried restarting but same problem.
Can you please advise what i should do?
Can't believe its such a headache to install twrp this device (and then later remove the bl warnings
Thanks
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
as it still gave the bootlocker warning, i turned oem lock on again via long press up on download mode. this fixed all warnings and i can boot now without warnings.
when i go into developer mode now, there is no option to oem unlock again.
if i go into download mode, there is no option to long press up and unlock again
on download mode it says:
KG State: prenormal
OEM Lock: ON (U1)
how can I turn oem lock off again, so I can try to install twrp?
Please assist.
thanks
SOLVED -
managed to turn oem unlock option again by turning off auto time update and setting clock back 10 days.
then on restart, the option appeared again and was set to oem unlock ticked.
went into download mode and i could see option again to unlock booloader.
long pressed up and it unlocked bootloader, erased data and restarted to system....
now... lets try to install twrp again and hope it doesn't give me 'unofficial binary' error due to SG prenormal state.
lol.. its KG STATE not SG fyi
Typo
lawmanukdc said:
Typo
Click to expand...
Click to collapse
lol id believe that in 1 comment but everywhere? oh well no biggie lol.. hope ur enjoyin ur phone now
How did you succeed to get the stock reinstalled ? Was it different version ?
lawmanukdc said:
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
Click to expand...
Click to collapse
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk