Hey there, I have a Samsung Galaxy Note 4 that I can't boot up. When I try to turn it starts the boot process but is immediately interrupted by a screen I can't get passed, this screen says "Custom binary blocked by Reactivation Lock" the below that in red "SECURE FAIL: KERNEL" with a yellow triangle in the center of the screen. I've tried factory resetting, and wiping cache partition but nothings worked. Someone please help me I can't get turn on my phone and I'm starting to freak out because I haven't seen any solutions anywhere. Thanks in advanced
brianggg said:
Hey there, I have a Samsung Galaxy Note 4 that I can't boot up. When I try to turn it starts the boot process but is immediately interrupted by a screen I can't get passed, this screen says "Custom binary blocked by Reactivation Lock" the below that in red "SECURE FAIL: KERNEL" with a yellow triangle in the center of the screen. I've tried factory resetting, and wiping cache partition but nothings worked. Someone please help me I can't get turn on my phone and I'm starting to freak out because I haven't seen any solutions anywhere. Thanks in advanced
Click to expand...
Click to collapse
try to install stock rom using odin
just google it and follow the steps
hit thanks
Related
So the phone worked fine when I bought it 2 days ago other than red text on top of the screen that said "binary is not seandroid enforcing". I looked into it and figured it meant the phone was rooted and custom. I picked up a nano sim today and the phone would not reboot. it started getting stuck saying "binary is not seandroid enforcing" and "custom binary blocked FRP locked". So i tried to flash back to stock rom with ODIN3 3.10.7. On the download mode screen it notes a custom binary and custom system as well as knox warranty void. So i try to flash N920TTMB1BOH6 first in the AP in ODIN3 and fails. Then i try to flash N920TTMB2COKC and it starts gets through some stuff and then fails; but it keeps my phone with a progress bar as if it is still installing but ODIN3 has failed out. So I exit ODIN3 and unplug the phone and now it will not turn off or start up into the boot loop. its stays on an error screen "an error has occurred while updating the device software use the emergency recovery function in smart switch". Smart switch did nothing. i put in the model and SN and it started to go to work and failed out after downloading info and gave me not emergency recover code. the only thing it can get into now is download/recover mode and when it is there is notes that the binary is now Samsung Official while the system is still custom. How do i get past this? I have attached a few screen shots of my issues.
Any help would be sooo awesome or I'm out way more cash than I'd like to be. :crying:
Josh
Message me ...I will help actually check your msgs I'll send u one
Sent from my SM-N920T using XDA-Developers mobile app
did you get it working yet
joshd00 said:
So the phone worked fine when I bought it 2 days ago other than red text on top of the screen that said "binary is not seandroid enforcing". I looked into it and figured it meant the phone was rooted and custom. I picked up a nano sim today and the phone would not reboot. it started getting stuck saying "binary is not seandroid enforcing" and "custom binary blocked FRP locked". So i tried to flash back to stock rom with ODIN3 3.10.7. On the download mode screen it notes a custom binary and custom system as well as knox warranty void. So i try to flash N920TTMB1BOH6 first in the AP in ODIN3 and fails. Then i try to flash N920TTMB2COKC and it starts gets through some stuff and then fails; but it keeps my phone with a progress bar as if it is still installing but ODIN3 has failed out. So I exit ODIN3 and unplug the phone and now it will not turn off or start up into the boot loop. its stays on an error screen "an error has occurred while updating the device software use the emergency recovery function in smart switch". Smart switch did nothing. i put in the model and SN and it started to go to work and failed out after downloading info and gave me not emergency recover code. the only thing it can get into now is download/recover mode and when it is there is notes that the binary is now Samsung Official while the system is still custom. How do i get past this? I have attached a few screen shots of my issues.
Any help would be sooo awesome or I'm out way more cash than I'd like to be. :crying:
Josh
Click to expand...
Click to collapse
did you get your phone working yet, i might be able to help you,,, i wont be avaibable till after the shabbat is over friday sundown to saturday sundown
I got it fixed. I just had to try it on a different computer. Ridiculous.
Sent from my SM-N920T using XDA-Developers mobile app
Samsung Galaxy S6 SM-G920I
Version Lollipop 5.1.1
Long story - My S6 suddenly died. When I tried to turn it on, it would turn on with the logo screen " Samsung Galaxy S6" and freeze right there and then after probably 30 seconds it goes black and then the logo again; forever and ever until the battery goes flat. Doing the physical button combinations did not work. FLASHING STOCK ROM DOES NOT WORK EITHER(and yes I did check that it is the right ROM) I'm able to go into download mode but the thing is:
Since my phone died SUDDENLY:
- DEVELOPER OPTIONS IS NOT TURNED ON
USB Debugging shouldn't have been on.
-I don't know but something to do with turning off OEM unlocking? and/or any other knox or something that blocks rooting, installing recovery etc.
Because of this, when I tried installing TWRP recovery or SpaceX kernel, it says "Custom Binary(RECOVERY) Blocked By R/L"
Tried searching up Google but only came with one English post and did not get much info out of it. The rest were about FRP etc and the way they had it was different from mine.
So now my phone is stuck. Any help? I don't mind voiding my warranty so go ahead with crazy methods that might work.
TL;DR
S6 suddenly dies, frozen at logo screen. Developer options is not enabled> USB DEBUGGING not enabled. Flashing STOCK ROM doesn't work. No recovery. Installing TWRP or SPACEX KERNEL is "Custom Binary(RECOVERY) Blocked By R/L"
Any help?
***EDIT***
DOWNLOAD MODE DOES WORK***
bump
bumpppp
bumpittybump
Seriously... No one is helping...
Hello, I have a Samsung Galaxy S6 It was working fine until recently when i try to root using cf autoroot i got bootloop. Anyway, I tried flashing the rom on in to a 6.0.1 and i also get that DM-Verity Need to check drk error... But mines a bit different.. I flashed the most recent 6.0.1 onto the phone from SamFirmware just fine... When the phone restarted it starts the blue "update" screen with a loading bar. It gets to about 24% then jumps to about 32% and briefly says "erasing" and restarts once more... It then proceeds to say something along the lines of "Supported api: 3" in white and "E:failed setting up dirty target" in red.. at the recovery type screen. I can then restart the phone to VERY BRIEFLY see the blue "updating" screen and then i get the final error i see which is the DM-verity verification failed... need to chekc DRK first.... So i have NO IDEA What to do next.. i tried also to restore my phone with samsung smart switch but no luck
One day, my phone just suddenly froze. Gave it a day to be left alone and it probably ran out of battery. Upon charging and trying to turn it on, it gets in a bootloop. It is NOT even getting past the very first logo at the start. It just shows "Samsung Galaxy S6 Powered by android" then freezes there.
I boot it into download mode and was unable to flash ROMs, Recoveries or Kernels. It has Reactivation Lock on!
"Custom Binary blocked by RL"
I gave up after this, but then I came back after months. I want to see if I can bring this phone back to life again. I've recently found this video where it has Odin 3.11 that had an option to disable Reactivation Lock!
https://www.youtube.com/watch?v=nt3VM3nd02U
I tried flashing TWRP and SpaceX kernel and it worked! It said pass, I saw the download bar in my phone fly across to completion and it did not show Custom Binary blocked by R/L again! Okay so... What now? It's stuck at the very same boot logo freeze. I STILL can't boot into TWRP recovery. I cant do anything. Is it HardBricked? Is it something to do with my EFS or Partition or whatever? Please help.
B U M P
My S7 has suddenly rebooted and now it won't go pass Samsung logo. At the first few reboots I was able to see PIN unlock screen where it would eventually freeze and automatically reboot, but now as I removed SIM and microSD it will only boot to Samsung logo in best case.
I have tried to enter recovery mode, but it freezes after 7 seconds at initial screen stating "updating system files". I can only successfully enter download mode.
What should I do? The warranty is not valid anymore, could I flash it with odin? Is there any way to recover data from internal memory? Please help.
krneki10 said:
My S7 has suddenly rebooted and now it won't go pass Samsung logo. At the first few reboots I was able to see PIN unlock screen where it would eventually freeze and automatically reboot, but now as I removed SIM and microSD it will only boot to Samsung logo in best case.
I have tried to enter recovery mode, but it freezes after 7 seconds at initial screen stating "updating system files". I can only successfully enter download mode.
What should I do? The warranty is not valid anymore, could I flash it with odin? Is there any way to recover data from internal memory? Please help.
Click to expand...
Click to collapse
Hey, same problem here !
I have, in addition of all that, the famous "Black screen & blue led" issue when i try to boot up my S7.
But my phone keep freezing when he try to boot. Keep freezing and rebooting 30 seconds after i unlock the screen with the pin (when he can boot), and for the recovery, it works for me, but only once in ten ...
Every times he freeze at the boot, i must wait when the battery hae 0% and shut down automatically
i already tried to wipe cache, but the situation doesn't change anymore.
i don't know too how to recover the internal storage data ...
If someone can help us .. :fingers-crossed:
(For me, my phone is entirely stock, and never flashed)