So I enabled secure start-up then flashed a Sammobile stock Rom using Odin. Stupid mistake. The phone now gives me a warning saying that the phone has secure start-up on it and I need to factory reset. There is then the option to reset at the bottom. This just then reboots to the same screen repeatedly. I then flashed TWRP to reset the phone that way but that immediately runs a script to send me back to the secure start-up constant reboot. So I need to somehow remove this Rom I think. Unfortunately TWRP is out becuase of the script that runs
I'm not changing any options in Odin. Maybe I should?
Can one of you awesome guys help me please. Is there a flashable Odin Rom that will skip this secure start-up message....?
Related
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!
Hi,
I am trying to install open recovery on my note 4 n910c android 5.1.1, using odin and openrecovery-twrp-2.8.3.0-treltexx.img.
Odin says that the flash is successful, but when I try to reboot in recovery mode I obtain the green android and after that the laid down android with 'no command' message to finally ending up in the normal recovery mode.
I have tried several methods to flash it, I even tried to root the phone (I had boot loop and reflashed the stock rom).
Can anyone help.
Thanks in advance
Hello,
Did you have the autoreboot option UNCHECKED in Odin when you flashed the recovery? it must be unchecked, the device can not be allowed to reboot into system after flashing. After flashing with the option unchecked and you get the green pass, you have to manually boot the device to recovery with the button method, then you will keep the recovery, if you boot it to any other modes immediately after flashing then it reverts back to stock recovery, it requires booting directly to the recovery immediately after flashing, then it will be retained.
Hi,
Well it make sense, I had the reboot option ticked on. I actually went through another way by flashing the 5.0.1 bootloader which then allowed me to flash the custom recovery.
To be honest I am not sure whether or not I had the reboot option ticked on (my guess would be that it was as it's the default option in Odin).
Anyway, thanks for the tips I hope it will help others.
i have verizon s7 edge. nougat. attempted to use odin to load engineering bootloader. succeeded and proceeded to reboot phone. then stuck in a boot loop. (tries to boot, vibrates, then tries again). tried to wipe cache partition and do factory reset w/o resolution. cant force power off but somehow stumbled into mode to boot into safe mode which also did not work. phone not rooted, was loading above to unlock (obviously). of note, did just update to nougat the day prior to doing this but phone working fine (although slow) after the update. any help appreciated.
ok...flashed factory rom and now working fine. still not sure what i did wrong to crash it initially. any ideas welcome.
Make sure your using the correct eng boot for nougat.
After fresh rom flash set up phone go to settings developer options and make sure oem unlock is checked.
Flash eng boot in ap slot.
Let phone reboot and start back up then you can run root.bat
Long story short - when using wifi my s7 edge started to restart several times until it got to boot loop. I tried various things, enter and exit download mode, factory reset, partition cache clear, nothing helped. I tried to flash stock firmware several times (different versions) but it didn't help. I can go to recovery and download mode, odin recognizes the device and passes the flashing, however it does not boot. Always stuck on "galaxy s7 edge" screen.
Do you guys have any idea what could I do? I was thinking about installing twrp, however will I be able to install it if the setting in developers setting "OEM unlock" was not enabled?
heofizzy said:
Long story short - when using wifi my s7 edge started to restart several times until it got to boot loop. I tried various things, enter and exit download mode, factory reset, partition cache clear, nothing helped. I tried to flash stock firmware several times (different versions) but it didn't help. I can go to recovery and download mode, odin recognizes the device and passes the flashing, however it does not boot. Always stuck on "galaxy s7 edge" screen.
Do you guys have any idea what could I do? I was thinking about installing twrp, however will I be able to install it if the setting in developers setting "OEM unlock" was not enabled?
Click to expand...
Click to collapse
Hello,
You don't have to worry, your phone isn't broken, i flash roms every day so i'm very familiar with does kind of "Errors". I'm here to assist you.
So without the OEM Unlock option enabled your phone won't be able to boot to recovery neither system if you flash a custom rom, flashing the stock firmware via Odin is the only way so try does steps:
1. Download stock firmware for your model from sammobile.
2. Extract the files and place them in the correct tab.
3. Disable auto-reboot in option panel.
4. Soon after it finish flashing, long press volume down and power button until screen turns off, then quickly press volume up, home button and power button.
5. Phone should now boot to recovery from which you have to do a factory reset and wipe cache/data.
6. Restart system.
Phone should boot just fine now, it might take 5 minutes for the first boot, if you're stuck for more than 5 minutes i would kindly ask you to take a picture of your log in recovery.
If you manage to boot the phone go to developer settings and enable OEM unlock then you can flash TWRP and from TWRP a custom rom.
If you have questions and still need help, feel free to pm me for anything, i'm here to help you!
Grettings,
SwitchDeath
So I took it to the service, it was a faulty motherboard.
I have same issue with my s7 edge, but with AT&T version (G935A). I couldn't find the firmware from sammobile as previous instruction from SwitchDeath. Do I have any other option to download the firmware from other source? Nothing seem to work for me from all other forum instructions and downloads, it just stuck in "galaxy s7 edge" screen on and off and not reboot at all. Please help!
I have a Samsung S7 Edge that kept rebooting itself randomly. I thought it might be due to a corrupt update. As time went by it started to bootloop several times before booting properly.
I managed to remove my Google account to disable FRP but I didn't manage to activate the secure startup pin before flashing.
Used Odin 3.14.4 and downloaded the BTU version of the firmware, but I later realised that the version used was XEU. Does that matter at all? Once the flash completes it auto reboots and begins bootlooping again. I have tried to clear cache partition and also factory reset via recovery menu. It again starts bootlooping many times, until it reaches the following screen that says;
Encryption failed. Unable to start up your device. The encryption process was interrupted. You need to reset your device to factory default settings. This will erase all your data. [Reset].
Click to expand...
Click to collapse
What else can I do here? I have not tried changing any settings in Odin, I left it at its defaults.
I am also unable to flash TWRP, as I understand I would need to unlock the bootloader beforehand and I'm not able to get it to boot.
Any luck? Its too late though