XDA user since 2007.
These last months I used to have a custom rom on my encrypted note 5 with no issue.
Until last week.
The phone refused to start after a shutdown ("Custom Binary block by FRP lock" message)
Just a black screen with this red message, really so at first it was kind of a malware before I knew about this 5.1 android feature that lock the phone in case of being stolen or modified.
What is really interesting is that Google guys implemented this "feature" obviously without taking in account encrypted users. So the message asking for the google account never appeared.
Ok. I make backups, it is not a big deal and I will flash a new rom with ODIN.
But then I realize it is impossible. This feature is specially made for preventing fresh factory reset.
The new roms + kernels I tried to flash (from 5.1 to 6.0) always display this message :
( device does not have DRK (device root key ), contact to SW PL
please flash ENG binary then install DRK
So I am basically screwed, and my phone is absolutely useless like it was stolen. Expect I paid $700 for it.
Really pissed of against Google and Samsung !!
The option to avoid this mess was : OEM unlock, I strongly suggest you to activate it before trying custom roms.
Related
Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device
Hello fellas,
I have a SM-G930F running Super Stock Rom 2.8, rooted with Magisk 12. This morning I was a little high and worried about getting my device stolen (my S6 was stolen at gun point three months ago), so I disabled OEM Unlock and USB debug in Developer mode, in a crazy attempt to increase the security and make things more difficult for the thief. WRONG! I have really screwed things up.
Now I get CUSTOM BINARY BLOCKED BY FRP LOCK and my device won't boot. The DOWNLOAD mode shows FRP LOCK is ON, this means I won't be able to flash anything with ODIN because it will fail at writing (that is what the FRP Lock is for). I am at work and my computer has the USB ports disabled, so there's nothing I can do until I get home.
This guy did the same stupid thing, except that he wasn't high
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
I know that attempting a flash with ODIN can also cause this problem:
https://forum.xda-developers.com/showpost.php?p=71692103&postcount=25
As soon as I get home, I will attempt the Smart Switch Emergency Recovery Function and I hope everything will be OK. Since it was my google account logged in, I won't have any problems with FRP (theoretically, it will ask me to login with the last account used on the previous configuration).
[UPDATE] There is this ADB thing I am completely unfamiliar with, not to mention I have disabled USB debug on the device prior to this. This file will disable FRP Lock but I don't know the procedure.
https://www.androidfilehost.com/?fid=24591000424958372
Any help will be much appreciated. This is my only phone and now I can't use it.
Just Flash with stock frimware to make it worked than it will stuck on google lock account than try to find ways on youtube.
asadnow2k said:
Just Flash with stock frimware to make it worked than it will stuck on google lock account than try to find ways on youtube.
Click to expand...
Click to collapse
Thanks for replying. Flashing stock firmware with FRP Lock will cause a write failure, are you sure about this? I will try it as soon as I arrive home. I didn't get that part where it will get stuck on google lock account, the device is mine and the latest google account used before was my personal google account. Could you please provide more details to complete the process?
I am also considering Smart Switch Emergency Factory Restore, that is my last shot before taking it to repair shop.
Dear sir kindly be sure the software is latest/i mean firmware
Hi,
had my phone locked too. Smart switch worked, aftter flashing twrp same problem. Got a factory rom from sammonbile and flashed cp, bl and ap with odin which brought it back.
Regards,
dennis
demmis_ said:
Hi,
had my phone locked too. Smart switch worked, aftter flashing twrp same problem. Got a factory rom from sammonbile and flashed cp, bl and ap with odin which brought it back.
Regards,
dennis
Click to expand...
Click to collapse
asadnow2k said:
Dear sir kindly be sure the software is latest/i mean firmware
Click to expand...
Click to collapse
I managed to solve it using Smart Switch, the firmware update did the trick. After restoring the system asked for last used credentials on previous configuration, like it was supposed to. Since it was my personal google account, there wasn't any problem with FRP Lock. Now I have installed TWRP and Super Stock Rom 2.8 again.
Leason learned, I will NEVER deactivate OEM Unlock again with a Custom ROM.
Thanks to everyone, this thread can be closed now.
hemp_invader said:
I managed to solve it using Smart Switch, the firmware update did the trick. After restoring the system asked for last used credentials on previous configuration, like it was supposed to. Since it was my personal google account, there wasn't any problem with FRP Lock. Now I have installed TWRP and Super Stock Rom 2.8 again.
Leason learned, I will NEVER deactivate OEM Unlock again with a Custom ROM.
Thanks to everyone, this thread can be closed now.
Click to expand...
Click to collapse
hiiii can you help how to get out, i also have a private google account logged in plzzz help, i have also disabled oem mistakely
Thank You
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.
Had no idea the dev options needed to be left ON regardless after rooting, or it rejects the custom binary? Would have thought the FRP lock would have been bypassed with the rooting. Can't enter twrp recovery neither.
And to be 100% clear, phone is rooted. Dev option was unticked w/o realizing it'd retroactively lock the phone as it detects the non-oem firmware and refuses to boot, refuses recovery, refuses flashing.
Can I somehow flash a stock firmare via Odin and NOT get the wrath of FRP? I found the stock firmware for the phone from Samsung's site. For some reason, the firmware.zip is like 1.4gb? Do I need to strip out a file for the recovery image assuming it'll accept it? Or just select the entire thing in Odin?
OK, flashed the 2.5gb (unzipped it had THAT much bloat) factory Samsung firmware, which took about 2.5 minutes vs. like 4 sec for the root .img :silly: and phone boots back up w/o issue, all personal stuff is intact, and unsurprisingly it adds all the bloatware back that I just deleted earlier.
So, if you accidentally turn off the dev options or I'm assuming the OEM unlocker specifically on your J7, and the phone refuses to boot as it's retroactively detecting "custom binary", OR if you happen to accidentally truly delete an important app and/or it can't be brought back with 3rd party apps, going to Samsung's firmware section, finding your EXACT phone/model/software numbers including the most recent OS and security upgrade to it i.e. 7.1.1 in my case, flashing it with Odin (site said to use most recent, so used v3.13.1) will restore the phone, unrooted of course. But it's better than a paperweight.
Hi, five nights ago, my phone just turned off, and then, restart for itself, but whit the "Blocked by FAP lock" message.
This is not the first time that happened this to me, because I forget to enable the OEM unlock, but is the first time that made it out of nowhere. I'm now with Android Lollipop.
That's the reason why I mades backups of my phone every week, but this week don't (I mades it every sunday), and have so important information on my device that I can't lose. In fact, the device is in my desk, I'm without phone since then.
I know that flashing the firmware will recover the phone, but doing that I lose the data.
There's a method that can recover the data first. And then flash the firmware?
Please, is so important.
Thanks so much.