So after doing a bunch of file rearranging, My bl now says 10.9A (2012-08-27). But in order to do this, I had to flash it with the system of 4.4.2. So the BL is downgraded, but the "Get started" screen after booting up is completely frozen so I can't enable debugging to root or do motocolyps to unlock. What can I do?
Related
Edit: No one replied with a good answer so i reinstalled stock recovery while keeping root and turned off OEM Unblock and it bricked my device with "custom binary blocked by frp lock" and i am currently fixing it with Smart Switch initialization. Moral of the story: Never disable OEM Unlock
(A5 2016)
Does this happen after you turn off OEM Unlock because the recovery is not stock (TWRP is installed) or because the device is rooted or both?
If after rooting with https://forum.xda-developers.com/sa...overy-samsung-sm-a510f-fd-exynos7580-t3314399 i flash stock recovery and turn off OEM Unlock will i still get this message?
Thanks!
Please note that i had the "custom binary blocked by frp lock" error but i fixed it with Smart Switch initialization. I want to turn off OEM Unlock for security reasons
just flash previous firmware version which u have in your phone before frp lock.
nothing to worry its not bricked.
only ensure version u are going to flash is same as before , flash via odin and enjoy
I already did it, my question is that if i remove TWRP and install the stock recovery while keeping root, will disabling "OEM Unlock" show "custom binary blocked by frp lock"
Help
I am going through a similar enigma. I have S7 Edge. If I log in with Google and then turn down unlock on will I get custom binary error? Any help would be greatly appreciated.
@CrystalGTX
This is an old thread, but I am having the same problem; (stupidly) unchecked OEM Unlock. Reboot, and now I have "Custom binary blocked by FRP lock".
When you say "fixed it with Smart Switch initialization", does that essentially mean reflashing firmware?
And as a result, erasing all data?
I've read that flashing stock firmware can save the hardware, but I'm much more concerned about the data; I need my contacts, photos, txts, etc.
EDIT: Err, shoot. I see now this was posted by a Guest, so I doubt the OP is going to give me a response. Anyone else help?
soooo.. full FRP lock
SM-G550T1 (metropcs)
limited odin
BL/AP Fail.
CP and CSC Write
Promts during boot to go to smart switch can not get S/N from sticker
Cannot boot into recovery FRP locked
Bootloader cant boot FRP Locked
Ideas?
Codebreaker32 said:
soooo.. full FRP lock
SM-G550T1 (metropcs)
limited odin
BL/AP Fail.
CP and CSC Write
Promts during boot to go to smart switch can not get S/N from sticker
Cannot boot into recovery FRP locked
Bootloader cant boot FRP Locked
Ideas?
Click to expand...
Click to collapse
What firmware are you on? You can't boot into recovery, but does your phone boot into the OS and through to the Google verification screen?
Drunkpilot said:
What firmware are you on? You can't boot into recovery, but does your phone boot into the OS and through to the Google verification screen?
Click to expand...
Click to collapse
Nope
Samsung On5 Screen with strictly in text upper left Custom Binary Blocked by [FRP] then it loops boot
Codebreaker32 said:
Nope
Samsung On5 Screen with strictly in text upper left Custom Binary Blocked by [FRP] then it loops boot
Click to expand...
Click to collapse
Funny enough, the exact same thing happened to me this afternoon. I had turned off "OEM unlock" and "USB debugging" in developer options and rebooted. I know exactly what you're talking about and I fixed it. I used Odin and flashed the 4 files with "nand erase all" checked in options. I flashed the G550TUVS2APL1 firmware. That is the rom I was on. I had previously tried flashing the G550TUVU1APF1 firmware for another issue and like you, I could only get the CP and CSC to pass, everything else was fail and it broke the modem and left me with no reception until I flashed the correct modem once again. The firmware you flashed was not the correct one. Flash the correct one and you will see your phone reboot into the startup wizard once again. Two minutes and my phone was up and running once again.
G935F FRP lock out of nowhere, "Device does not have DRK" after stock firmware flash
Hello. I and my friend have a lot of problems currently with the phone.
The phone had randomly thrown the FRP lock on, and it became unbootable. (gets stuck at logo and would tell that "custom binary locked by frp lock"). The phone previously had stock firmware.
The first fix we've attempted was to flash the stock Oreo firmware (G935FXXU2ERE8) via Odin. But after flashing, It got stuck at bootloader logo without any additional text this time.
Then we've tried to flash an older firmware (G935FXXU2DRC4), and then the phone started throwing the "Device does not have DRK" error.
After booting to recovery, it says "Please flash ENG binary then install DRK".
After reboot via recovery, it started throwing a dm-verity error (0x02).
After some Googling I've found out that It's fixable with a boot file flash. But I couldn't find one for current firmware. Maybe we could just use combination sboot file (pakfirmware.com/2017/11/samsung-frp-samsung-s7-edge-g935f-sboot-combination-file), or should I find one that's specific to the current firmware?
Hi i want to downgrade the Bootloader.
I am on Oreo 8.0, is it possible?!
I have try arround with Factory Binaries but no luck,
edit:
Okay, now i have a RPMB PROVISIONING at boot and nothing happens.
When i try odin mode sometimes i see a red colored text ......bootloader exception.....blablablalbalblaalbaa
And after a few attempts i came into odin but i cannot flash the bootloader with odin.
Everytime fails!
BUJ1 fw. I had previously rooted the device and it was working fine, then x days later found it wouldnt boot (teal screen with 'enrolled knox guard prevent flashing factory binary (vbmeta)' displayed) so I reflashed the stock binary. Now when I go into dev options, I cant get OEM unlock to appear (tried the date forward/back.. didnt work). Anyone know how I can fis that?
Additionally, in download mode the tab shows 'oem lock off (u)' and 'kg status normal', but when I try to flash the magisk modified ap file to root it, it fails almost at the end of the odin process with the 'enrolled knox guard prevent flashing factory binary (vbmeta)' error displayed on the download screen. Rebooting then boots back into the stock android. Is this likely to be linked to the owm unlock being unavailable in dev options even tho the device is showing oem lock is off?