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
Related
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
I bricked/bootlooped my phone.
I've been using Superman ROM v2.4.1 for a while, but recently my Snapchat stopped working and I couldn't pass the SafetyNet, so I tried to fix it.
I turned off my developer options, and downloaded this App: https://forum.xda-developers.com/sho....php?t=2524485
My phone warned me this App might be harmful but I ignored it, and then changed the setting to permissive and then enfordcing a couple times. Then I rebooted my device, now it is stuck in a loop. It doesnt go beyond the 'Samsung Galaxy S7" logo and just turns off after that.
I cannot boot into recovery either, only download mode.
When i try to boot up or into recovery, it says on the top of the screen in red text "Custom Binary blocked by FRP Lock".
Can anyone help me? I have a flight in the morning so I really need this fixed. Is this caused by the App I used to change the SELinux Mode? Or is it because Developer options and hence OEM Unlocking is turned off in the settings?
What can I do to fix this?
Cheers
Dear Sir just Flash with stock firmware be sure u are using latest one to revive phone back to life.
thanks
FRP locked and cannot load stock FW
I'm having the same issue as theDroidfanatic, but i cannot flash the stock FW.
I have a Samsung S7 edge, running Superman, i believe marshmallow (i don't recall the exact version).
I accidentally enabled the OEM lock in the phones settings.
On trying to boot normally, I see the superman startup screen, and the FRP message across the top of the screen in red. "Custom Binary blocked by FRP Lock"
I can only boot into download mode.
Odin (3.12.7 and 3.12.3) can detect the phone being plugged in (so i think this system has the correct drivers, and my cables/ports are good).
I downloaded the latest FW from sammobile.com for the MTA region (its a Canadian MTS phone).
I load all of the files into Oden and everything appears fine. When i try to start the transfer it hangs at SetupConnection. Ah hour later, its still hanging there.
I've tried 2 PCs, and about a dozen USB cables; same result every time.
Its been a while since i played with rom stuff, am i missing something somewhere?
## EDIT
## Above represents 8+ hours of frustration;
## below, 20 minutes on a hunch and some dumb luck;
## proving that sometimes it is better to be lucky than good.
For anyone else having similar issues:
After installing Kies (on Windows 10; which required a Microsoft Virtual C++ pack for Kies to install), Kies installed a different USB driver.
Odin did not show any difference regarding seeing the phone. After the new driver was installed, Odin is now able to flash stock FW.
Did you manage to repair your phone. My note 9 don’t show up on my laptop usb not recognised
I had similar issue when i was trying to install firmware while developer mod was was disabled (in my Note 5). FRP lock was ON, then it got bricked. I gave my phone to a local phone repair shop, they have some technology to bypass FRP lock by using FRP bypass box.
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 phone began lagging last night so I gave it a restart. The shut-down animations were normal but when the phone turned back on, it gave me the dreaded FRP LOCK curse. I went through many forums and videos and I was able to take the lock off via FRP Hijacker, but now I am stuck at the download mode. If I try booting the phone on with the stock recovery, the Samsung Note5 splash screen stays indefinetly (soft brick). If I try booting the phone with a custom recovery, I get a message in purple text saying "Recovery image signature check fail. Reboot to avoid Warranty bit set" and it will keep bootlooping. Currently, I am not sure how to continue if I cannot get to the recovery mode and flash a ROM. So basically, I am stuck at not being able to flash a rom, nor being able to get into recovery mode successfully without a brick or bootloop. Any help is greatly appreciated.
Edit 1: USB Debugging is turned on as well as OEM Unlock
you need to use odin and downgrade to a stock 6.0 tar file..or use a conversion tar file taking you from n920p to n920f..or n920c ...ill upload the files everyone needs after work today...
Okay so I have a samsung galaxy a03s and I wanted to root it but it would appear that's not easy. So I then try to install lineage because that's rooted, but that's not very easy either so I try flash twrp because I think you need that first, and somewhere in between all that I seem to have broken the phone. I get the "error while updating system software" error, I try to fix it with smartswitch and it says this device is not compatible or something and won't fix it. I try Oden and I get the "sw rev check fail vbmeta fused 4 binary 2 rp check error vbmeta". Honestly idk what I did to it but I need help fixing it so if you could help me that would be awesome! Thanks.
Okay so update. I was able to flash the phone with Oden but now the phone just keeps boot looping, where it just turns on and the samsung logo flashes then turns back off, then it keeps doing it over and over.
Final update: I left it boot looping for a bit and then it said samsung.. then it said erasing. It restarted and booted. I think I finally fixed it almost a year later.
Wondering why you started this thread?