Database Users

Dev Ed with Reactivation Lock on Recovery - please help!

Ok, this is my first dev device and I don't want to screw it up.
But, now I screwed up. I was SO comfortable running a new ROM that I messed around and checked on Reactivation Lock.
But then, I got a wild hair to try the TouchWiz 4x5 launcher instead of Nova and booted into Recovery to flash it in.
Now, I get "Custom binary blocked by Reactivation Lock"
Crap Crap Crap....
I've looked at several threads about how to boot or flash to fix, but the solutions seem ambiguous at best.
My biggest fear is that I am running a dev device and I don't want to get the wrong firmware and end up flashing in a retail bootloader or something.
Please Help!
I've tried pulling the battery, booting in download mode but neither of those work.

Rickinsav said:
Ok, this is my first dev device and I don't want to screw it up.
But, now I screwed up. I was SO comfortable running a new ROM that I messed around and checked on Reactivation Lock.
But then, I got a wild hair to try the TouchWiz 4x5 launcher instead of Nova and booted into Recovery to flash it in.
Now, I get "Custom binary blocked by Reactivation Lock"
Crap Crap Crap....
I've looked at several threads about how to boot or flash to fix, but the solutions seem ambiguous at best.
My biggest fear is that I am running a dev device and I don't want to get the wrong firmware and end up flashing in a retail bootloader or something.
Please Help!
I've tried pulling the battery, booting in download mode but neither of those work.
Click to expand...
Click to collapse
I've got reactivation lock enabled and haven't had any issues.
Ok..
When did you get the "Custom Binary blocked......" message? After booting into recovery? After flashing the file? What recovery?
When does the message appear? After the Samsung splash screen? After the boot animation? After the device boots completely?

MrHyde03 said:
I've got reactivation lock enabled and haven't had any issues.
Ok..
When did you get the "Custom Binary blocked......" message? After booting into recovery? After flashing the file? What recovery?
When does the message appear? After the Samsung splash screen? After the boot animation? After the device boots completely?
Click to expand...
Click to collapse
Sorry, I could have been more detailed to save this.
The S5 has TWRP for recovery (2.7.0 I think). I downloaded TouchWiz4x5.zip and restarted into recovery via QuickBoot app.
When the phone starts, I get the familiar Samsung logo, S5 Custom Android screen, not boot animation. It displays for about 2 seconds and then up in the top left it reads:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then displays:
Custom binary blocked by Reactivation Lock
SECURE FAIL: RECOVERY
...and goes no further. This whole boot process takes like three or four seconds from power on to yellow triangle ( I call it the ROMuda triangle lol)
I was thinking if I could force the boot loader to boot normally instead of into recovery all would be fine. It's getting hung on TWRP recovery. Then I could turn RL off. Some of the threads with similar errors have SECURE FAIL: KERNEL, which is not what I'm dealing with. The kernel and firmware are fine.
If I do have to return to stock, then I need to make damn sure that I'm flashing a dev edition so I don't end up with a retail version and locked boot loader.

Rickinsav said:
Sorry, I could have been more detailed to save this.
The S5 has TWRP for recovery (2.7.0 I think). I downloaded TouchWiz4x5.zip and restarted into recovery via QuickBoot app.
When the phone starts, I get the familiar Samsung logo, S5 Custom Android screen, not boot animation. It displays for about 2 seconds and then up in the top left it reads:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then displays:
Custom binary blocked by Reactivation Lock
SECURE FAIL: RECOVERY
...and goes no further. This whole boot process takes like three or four seconds from power on to yellow triangle ( I call it the ROMuda triangle lol)
I was thinking if I could force the boot loader to boot normally instead of into recovery all would be fine. It's getting hung on TWRP recovery. Then I could turn RL off. Some of the threads with similar errors have SECURE FAIL: KERNEL, which is not what I'm dealing with. The kernel and firmware are fine.
If I do have to return to stock, then I need to make damn sure that I'm flashing a dev edition so I don't end up with a retail version and locked boot loader.
Click to expand...
Click to collapse
Sounds like reactivation lock flagged your custom recovery. Can you get into Download mode? Start your phone like your trying to load Download mode. When you get the screen for Vol UP or Vol Down for continue or reboot, select reboot and see if it lets you boot up. If it does, then disable reactivation lock.
If it still won't boot, you should try flashing your stock recovery via ODIN. Hopefully you've made backup copies as there are no official firmware packages for the DevEd. Alternatively, you could ask another DevEd user to give you a copy of their recovery.
Have a look at this thread: [ODIN-RESTORE] [GS5-DEV Edition] Flashable Rescue package

MrHyde03 said:
Sounds like reactivation lock flagged your custom recovery. Can you get into Download mode? Start your phone like your trying to load Download mode. When you get the screen for Vol UP or Vol Down for continue or reboot, select reboot and see if it lets you boot up. If it does, then disable reactivation lock.
If it still won't boot, you should try flashing your stock recovery via ODIN. Hopefully you've made backup copies as there are no official firmware packages for the DevEd. Alternatively, you could ask another DevEd user to give you a copy of their recovery.
Have a look at this thread: [ODIN-RESTORE] [GS5-DEV Edition] Flashable Rescue package
Click to expand...
Click to collapse
Hyde, the link for the rescue package is dead. I did make a full backup with TWRP but don't know how to use it to flash via Odin.

TWRP doesn't backup the recovery. You may need to send a PM to one of the other users who have DevEd.

FIXED!!!
Just wanted to follow up to let everyone know that I have fixed the "Custom binary blocked by Reactivation Lock" error that had bricked my device.
I downloaded the recovery file (I'll update with a link to this file)
I flashed with Odin 3.0.7 (PDA)
It FAILED. (I expected this)
I unplugged USB, pulled the battery out
I put it back in, booted into stock recovery with Power + vol down.
Selected Normal Boot
Everything Fine!
Went to settings and turned off RL. LOL
Restarted Phone with normal Power Off menu - still fine
After reboot, opened SuperSU, still showed QuickBoot with root access
Opened QuickBoot, tapped on Recovery
It booted into TWRP (I'm on 2.7.0.0) - no problems
Rebooted again. No more error when booting to custom recovery
Profit!!!
** the battery pull trick after Odin flash fail I picked up from the Note 3 forums **
** If you have SECURE FAIL: KERNEL, you may need to perform a factory reset during the first boot after battery pull! **
A big thanks to all those who helped me via the forums and PM!

[Q] Phone in bootloop, won't boot to Recovery

X-post from the noobies thread
While trying to install TWRP while I already had CWM, my phone is now in a boot loop at the Recovery Booting screen where "Recovery Booting" is at the top left in blue. I had been trying to install the GPE lollipop rom that was made for the spring galaxy s4. When I flashed TWRP from the app, it said it was successful. However, when it went to reboot it recovery it went into the boot loop. All help is appreciated, Thank You!
Edit: It now just stays at the Samsung Logo screen with the blue "Recovery Booting" at the top left.

Ophiuchus_New said:
X-post from the noobies thread
While trying to install TWRP while I already had CWM, my phone is now in a boot loop at the Recovery Booting screen where "Recovery Booting" is at the top left in blue. I had been trying to install the GPE lollipop rom that was made for the spring galaxy s4. When I flashed TWRP from the app, it said it was successful. However, when it went to reboot it recovery it went into the boot loop. All help is appreciated, Thank You!
Edit: It now just stays at the Samsung Logo screen with the blue "Recovery Booting" at the top left.
Click to expand...
Click to collapse
It might be a little late but I had the same issue while attempting to mess with recoveries at work (no computer access). I managed to get my phone to boot by pulling the battery out and holding down the power, home, and volume down buttons while booting. When it gives you the custom OS warning press volume down to boot normally again. Hope this helps someone!
Now my problem is trying to get one recovery to boot when I get home. Wish me luck!

i need emergency help to my constant recovery boot loop without any recovery mode.

hello, i think i just bricked my note 3. i accidentally boot the phone into the recovery mode on my sm-n9005 singapore lte version.
i downloaded this application called Quick Boot (Reboot) by GHCV on google play store. upon opening up the application and selecting the "Recovery" mode, it rebooted my phone into the recovery mode but there is a problem. it keep on saying: "Recovery is not SEandroid enforcing set warranty bit: recovery" and it constantly stuck in the recovery boot loop ever since then till now. my note 3 sm-9005 5.0 version is rooted by kingo root. i tried to install TWRP into my note 3 but failed, on the odin 10.7 it showed that it is successful but on my phone it doesn't even go into TWRP recovery mode. i tried these steps but all failed: pull out battery then press volume down, power button and home button for awhile then put in battery; boot it into download mode then press volume down to restart but still it brings me to recovery boot loop. i cannot even go and hardware reset my phone anymore. please help me i need my this phone urgently as this is my every day phone. i didnt flash CWM too as i ran out of time. please reply me as soon as possible to my email [email protected] thanks. urgently needed help.

mastermind_tan said:
hello, i think i just bricked my note 3. i accidentally boot the phone into the recovery mode on my sm-n9005 singapore lte version.
i downloaded this application called Quick Boot (Reboot) by GHCV on google play store. upon opening up the application and selecting the "Recovery" mode, it rebooted my phone into the recovery mode but there is a problem. it keep on saying: "Recovery is not SEandroid enforcing set warranty bit: recovery" and it constantly stuck in the recovery boot loop ever since then till now. my note 3 sm-9005 5.0 version is rooted by kingo root. i tried to install TWRP into my note 3 but failed, on the odin 10.7 it showed that it is successful but on my phone it doesn't even go into TWRP recovery mode. i tried these steps but all failed: pull out battery then press volume down, power button and home button for awhile then put in battery; boot it into download mode then press volume down to restart but still it brings me to recovery boot loop. i cannot even go and hardware reset my phone anymore. please help me i need my this phone urgently as this is my every day phone. i didnt flash CWM too as i ran out of time. please reply me as soon as possible to my email [email protected] thanks. urgently needed help.
Click to expand...
Click to collapse
Home-Volume Down-Power = Download Mode
Home-Volume Up - Power = Recovery Mode
You'll need to flash the Bootloader and Recovery. It may start up at this point. If not, then flash the Singapore ROM. You can extract the bootloader and recovery and then make them a .tar .md5 file for Odin. Read about it HERE. I've used it to recover my Canadian SM-N900W8 Note 3. All it would do was vibrate and boot loop. Now I'm 100% back up and running in Lollipop. Only use files for your version of the Note 3.
http://www.sammobile.com/firmwares/database/SM-N9005/
Singapore has 4 cell providers to choose from.
Or
you can try using Samsung Kies . Tools > Emergency Firmware Recovery. You'll need the serial # under your battery.

Or you just flash this one https://idlekernel.com/twrp/3.0.0-0/twrp-3.0.0-0-hlte.tar.md5 by Odin on the AP slot. If you really have a SM-N9005 like me (No other strange SM-N900* one!) this will work and fix your loop by updating the bricked recovery to the most recent TWRP one. Here is more information I'd recommend to at least read a bit of to at least understand a bit what you are installing by that: http://forum.xda-developers.com/showthread.php?t=2467001
ODIN 3.09 for ya: http://androidhost.org/PVAIv (using old crap 1.85 is NOT NEEDED)

Odin 3 Root "PASS" Stuck on Samsung s5 logo

Heya
I followed a guide to download odin and CF auto Root-k3g-k3gxx-smg900h. I installed odin, booted into download and loaded the cf autoroot.
It takes a while before going to blue "RESET" and then my phone keeps showing the samsung logo.
After 2min Odin shows a green "PASS".
However I'm now stuck with a phone that won't boot and keeps showing the samsung logo.
I have tried the advice given in http://forum.xda-developers.com/showthread.php?t=2725939
Any advice would be appreciated.

After flashing with Odin did your recovery boot and do its thing, or did your phone reboot and just hanged on the Samsung screen? If the latter occurred, try repeat the entire Odin process again.

Heya.
I repeated the process, but while it says "Blue Reset" it's still sits at the samsung logo. The only way to then reboot is to take the battery out and put it back in. Then when I press vol up+pwr+home; nothing happens except the logo. No recovery mode.
The only thing that I seem to have access to is the Downloading.

Xi41 said:
Heya.
I repeated the process, but while it says "Blue Reset" it's still sits at the samsung logo. The only way to then reboot is to take the battery out and put it back in. Then when I press vol up+pwr+home; nothing happens except the logo. No recovery mode.
The only thing that I seem to have access to is the Downloading.
Click to expand...
Click to collapse
Flash stock ROM again with ODIN
Don't use CF AR to root again, some phones just brick like that
Flash TWRP recovery, then SuperSU from TWRP instead

Stuck in "Samsung Galax S7 Edge reboot loop after using Odin3

As the title says I tried to root my phone and got into this situation. I followed a video from TheUnlockr
I put my phone into developer mode and the OEM unlock.
I completed the Odin3 boot img using Samsung_G935x_QC_Rooted_BOOT.TAR file that I got from XDA developers. It said it passed
Afterwords I'm stuck in the reboot loop. I can get into the the teal custom OS download screen as well as the recovery booting screen that does the "Installing system update" animation and I get a "No Command" screen with a dead Android, after a bit it lets me into the Android Recovery screen. I've tried Reboot system now, no go, reboot to bootloader no joy that goes to the "Downloading... Do not turn off target" message.
I believe my bootloader got gorked with the rooted boot.
How can I get back to just a usable OS? I've downloaded the stock firmware from Sammobile but that's taking 2-3 hours. Am I just until that finishes downloading?

Yeah, wait until file finishes and than of course flash with odin. Sometimes Sammobile is slow, you may try downloading firmware from uptodato.com (if you've fast internet connection).