Hi i have tried to recover i9505 which was stuck on samsung logo assumed its just like another samsung phone so i downloaded any 4.3 firmware from internet and updated it using odin. Now phone is stuck at samsung logo with a message on top left corner recovery booting... I have tried different firmwares on it some of the were 4.3 but it still stuck there. on some firmware it gives error on odin and doesn't go further
state of the phone
can't boot into recovery holding vol + home +power
phone can go in to download mode
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection enabled
emmc Burst mode enabled
please help thanks
faisal_sherry said:
Hi i have tried to recover i9505 which was stuck on samsung logo assumed its just like another samsung phone so i downloaded any 4.3 firmware from internet and updated it using odin. Now phone is stuck at samsung logo with a message on top left corner recovery booting... I have tried different firmwares on it some of the were 4.3 but it still stuck there. on some firmware it gives error on odin and doesn't go further
state of the phone
can't boot into recovery holding vol + home +power
phone can go in to download mode
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection enabled
emmc Burst mode enabled
please help thanks
Click to expand...
Click to collapse
Hi there,
First try getting into recovery again!
Turn device off completely and leave for a minute or so......
Hold Power + Volume Up (no need for home button)
Wait for Vibration and Samsung Logo to appear then the writing in the top left corner....
Release the Power button but keep Volume Up pressed
Wait for Vibration and Samsung logo and writing to appear then let go of the volume rocker
Hopefully will boot to recovery
Factory reset the device and reboot......
If above fails try below............
You need to flash the latest firmware for your device........Which must be 4.3 firmware due to the KNOX boot loader you have, which if you did not know you have void your KNOX warranty 0x1 ( you cannot use the knox application anymore and this is currently irreversible ). Check what the latest firmware is HERE and flash through odin........If your phone is in boot loop after flashing or stuck at the logo then boot into recovery (if possible) and factory reset the device and re-boot.
Flashing any old firmware won't work
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!
Samsung S4 M919V
Rooted using Odin
CWM & Titanium Backup saved on MicroSD Card and External HD
Used cm-11-20140217-NIGHTLY-jfltecan.zip
Problem
Installed CyanogenMod
Phone is currently stuck in a boot loop
Regular Startup Sequence:
Cyanegen Mod boot logo appears
Android is upgrading
Optimizing/Starting apps
Unfortunately, the process has stopped working.
Restarts.
Recovery mode (Bottom Volume key, power button, home button
"Warning!!" page, Volume up: Continue.
Stuck at "Downloading... Do not turn off target!!
Top Left corner:
Odin Mode
Product Name: SGH-M919V
Current Binary: Custom
System Settings: Custom
Knox Kernel Lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30
Secure Download: Enabled
Write Protection: Enable
eMMC Burst Mode: Enable
Click to expand...
Click to collapse
Connected to laptop
Odin only recognizes phone with regular boot up.
I'd really appreciate any help or suggestions you guys have for me.
Thanks.
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)
My device build is MMB29M.G900MDUBU1CPG1
I tried CF Auto Root, but after i flash my device, in Samsung screen, appear on the top:
Recoovery booting
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I have tried to enter the download mode and to boot, but it did not work, he returns to this error, only solves after making the flash again from Android with Odin