Database Users

[Q] Phone bricked

Hey guys, I am really stuck. I recently flashed the leak to 4.4.2 and was happy until I dicided to root it using cf-route method.
I then tried to flash TWRP recovery using goo manager app.
To check if it was sucessful I decided to reboot into recovery and now I am stuck in a boot loop.
Cant get into recovery or download mode.
I get this:
Kernel is not seandroid enforcing
set warranty bit: kernel
Any ideas how to fix it.

shaazzaarr said:
Hey guys, I am really stuck. I recently flashed the leak to 4.4.2 and was happy until I dicided to root it using cf-route method.
I then tried to flash TWRP recovery using goo manager app.
To check if it was sucessful I decided to reboot into recovery and now I am stuck in a boot loop.
Cant get into recovery or download mode.
I get this:
Kernel is not seandroid enforcing
set warranty bit: kernel
Any ideas how to fix it.
Click to expand...
Click to collapse
Don't throw the word Bricked around so easily, your phone is NOT bricked
You made the error, if you read properly you would see that TWRP is not yet compatible.
Reboot into download mode (take the battery out to power the phone off) , then flash CWM by chenglu (you can search for it right?)
and it should fix your issue.
Before you start messing around with a £600 + device, you may wanna read up a bit, or you're gonna have a Samsung paperweight.

Finally working again.
radicalisto said:
Don't throw the word Bricked around so easily, your phone is NOT bricked
You made the error, if you read properly you would see that TWRP is not yet compatible.
Reboot into download mode (take the battery out to power the phone off) , then flash CWM by chenglu (you can search for it right?)
and it should fix your issue.
Before you start messing around with a £600 + device, you may wanna read up a bit, or you're gonna have a Samsung paperweight.
Click to expand...
Click to collapse
WOW, what a night. After countless boot loops I removed the battery and waited for a few minutes.
I put the battery back in, pressed volume down, power and home key at the same time.......and BINGO !!!
I was in Download Mode. Just flashed the leaked firmware again and didn't even loose any apps and data.
I guess lesson learnt, do your research before flashing anything.

shaazzaarr said:
WOW, what a night. After countless boot loops I removed the battery and waited for a few minutes.
I put the battery back in, pressed volume down, power and home key at the same time.......and BINGO !!!
I was in Download Mode. Just flashed the leaked firmware again and didn't even loose any apps and data.
I guess lesson learnt, do your research before flashing anything.
Click to expand...
Click to collapse

[Q] Galaxy S4 i9505 Bricked - No Recovery Mode - Stuck in Bootloop

Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards

menaum said:
Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards
Click to expand...
Click to collapse
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?

malybru said:
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?
Click to expand...
Click to collapse
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.

menaum said:
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.
Click to expand...
Click to collapse
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.

malybru said:
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.
Click to expand...
Click to collapse
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!

menaum said:
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!
Click to expand...
Click to collapse
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?

AT&T version here, same problem
malybru said:
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?
Click to expand...
Click to collapse
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie

ardonie said:
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie
Click to expand...
Click to collapse
Hi,
Then , you should try flashing a non-knox firmware .
Unfortunately ,I do not know AT&T firmwares.
Perhaps someone HERE can help.

I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here

recovery is not Seandroid Enforcing
lorenzoraj said:
I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here
Click to expand...
Click to collapse
I also have the same problem with Galaxy s4 Active (i9295)
Flashing recovery finish successfully (tried Philz,CWM, TWRP )
But afterwards no recovery exists anymore
only:
recovery is not Seandroid Enforcing
When I flash stock ROM again, the basic recovery it there - no option for applying zip files

Note 3 stuck on recovery boot

Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.

nrkid9 said:
Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
Click to expand...
Click to collapse
Use below file for rooting & once rooted successfully, switch off your phone & reboot in recovery.
http://d-h.st/J32

re: download mode
nrkid9 said:
Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
Click to expand...
Click to collapse
Remove battery, wait 10 seconds replace battery and
hold down the volume down+power+home key at the
same time. Then the phone will go into download mode.

I have 4 sprint Note 3's I rooted with CWM for all 4 but one is "stuck" at recovery like this any time I turn it on it always tries to boot into recovery and gets stuck.
I can get into download mode. will cf auto root fix this? (trying to avoid a full odin restore)
the only thing different about this sprint note 3 that I am aware of is that its flashed to boost (if that matters it should not matter)
the other 3 went flawlessly. yes I tried to odin the cwm root a second time no change.

Thanks!!!
Thanks for the link. Just unboxed the note 3 (sprint) with version 4.3 and followed qbking77 and it was stuck on that same screen (tried it 3 times).
Your link saved me. :good::good::good:
I wonder why qbking's didn't work ... it always has in the past.
jdomadia said:
Use below file for rooting & once rooted successfully, switch off your phone & reboot in recovery.
http://d-h.st/J32
Click to expand...
Click to collapse

chickenmusket said:
Thanks for the link. Just unboxed the note 3 (sprint) with version 4.3 and followed qbking77 and it was stuck on that same screen (tried it 3 times).
Your link saved me. :good::good::good:
I wonder why qbking's didn't work ... it always has in the past.
Click to expand...
Click to collapse
Why didn't you use the specific file for your device (Note 3 Sprint): http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip

thought I was...
Maybe I'm getting dumber, or maybe it's getting more confusing to root. Seems like there's a crap load of how to root this device pages and it takes a long time to figure out which one actually works. Then once I find it, I'm faced with dead links to the downloads.

I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks

Do you have access to a USB jig?

luqmaanki said:
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Click to expand...
Click to collapse
same problem here did you find solution please reply

As already posted .
Try USB Recovery Jig.
Fails then service centre .

twrp
vndnguyen said:
Why didn't you use the specific file for your device (Note 3 Sprint): http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Click to expand...
Click to collapse
i know this thread is old....but sometimes i have to access download mode, and then chose cancel in order for it to boot. usually from recovery when i tap reboot system, it brings me back to recovery. so i have to pull the battery and button combo to download mode then cancel. does this issue have any familiarity?

Someone please help I have a Samsung note edge that I just reset through the menu settings backup and reset option and phone turned off but did not fully come back on its just sitting on black Samsung Screen and on top left corner it says recovery booting set warranty bit : recovery in blue and yellow letters and I am able to got into the download screen but I press volume down just to cancel and reboot and stars coming on but gose back to same black Samung screen. Like i said I did not try rooting it or any such thing.

Wrong forum this is not EDGE model .
Download mode and flash stock rom through Odin is generic advice .

"Recovery Booting" Bootloop fix
A few months ago, my rooted Galaxy Note 3 (sm-n900t) was force closing and freezing my apps often. So I decided to boot into recovery to clear device cache. The 'recovery booting' would appear on the screen with the logo, but after 7 seconds it would reboot normally instead of opening recovery(I had version 3.2.3.0). So I did reboot recovery with Rom Toolbox and it began bootlooping with the message:
Recovery Booting....
Set Warranty Bit : recovery
It wouldn't boot normally, in recovery or download mode.
STEPS TO FIX:
1.) Let phone Bootloop until completely dead
2.) On PC downloaded (2.8.7.0) twrp file for device from twrp.me/devices
3.) Press and hold volume down + home + power until phone reboots into download mode.
4.) Plug device into PC USB where drivers are loaded.
5.) Start Odin or Samsung Tool z3x flashing tab
6.) Load twrp in AP or PDA section and flash
7.) Phone should reboot normally!

[q] help stuck in recovery loop

I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me

androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
Well based on the limited info you gave I'm going to assume you flashed a rom. Likely a bad download.
If so download a different rom or re download the rom and flash again. Make sure you're doing a full wipe. Also be sure you're on the latest stable recovery.
Worst case if all of the above fails, odin the stock rom and start over and you'll be fine
running DECEPTICON rom (coming soon)
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif

re: RECOVERY IS NOT SEANANDROID
androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
When you see "RECOVERY IS NOT SEANANDROID" as the phone
tries to boot or boots it's perfectly normal after the phone is rooted.
Here is a fix which works 90% of the time for most people with the same
issue you are experiencing with your phone.
Power down the phone, then power it backup while holding the
phone's power/volumeUp/home buttons down all at the same time
until you see tiny blue text appear on top of your screen, as soon as
you see that let go of all buttons.
The phone will boot into Recovery mode.
Once you are in recovery mode do a "factory data reset" or factory reset
which ever way the option is displayed.
After that the phone reboots itself and it should fully boot making the phone
ready to use.
Good luck!

androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
Take the battery out for a minute or so, then reboot into recovery. If no go, reflash your recovery (make sure you're using the right one obviously.
RECOVERY IS NOT SEANANDROID ENFORCING is normal when you have a custom recovery installed. It's just telling you that the official samsung signature isn't there. There's many threads regarding bootlooping around, a quick read probably would have sorted you :good:
PS: For the record, if you're getting physically sick about it, maybe you should read up a bit more before messing around with your very expensive device. I might sound awful but it's the truth.

Fixed It
The problem was i flashed the wrong recovery and my phone would not load or even go into download mode. I found somewhere online that if i held the download mode buttons before i put the battery in it would work and it did which allowed me to re flash my recovery.

[Q] S4 not booting past logo after flashing CWM

Hi everyone. I don't know if I'm posting in the right forum or not, but right now, I'm at the end of my rope and I've run out of things to try.
I lost my 18-year old sister last week in a car accident. I visited the accident scene with my parents and we found her phone. It was hard to
recognize amid all the scrap because of how mangled it was, but her S4 was there. Everything except the motherboard was destroyed, so we went
and put the motherboard into a new S4 to see if we could get any data from it. The phone worked for a while. It was able to boot to the lock
screen and it connected to our wifi whenever we walked into the house. However, it's passcode locked. We don't know the password to her google
account either.
I searched google for solution on how to unlock the phone, but the methods I found required that USB debugging be enabled, and of course, she didn't
have it turned on.
I found one method that could work. Aroma file manager. But it can only be flashed using Custom Recovery. Naturally I tried to flash CWM, and it
appears to have been successful (according to ODIN). But when I tried to boot into CWM, I got the "RECOVERY IS NOT SEANDROID ENFORCING" error and
the phone shut off. Now the phone can't get past the S4 logo. I'm not sure if this is a problem with the battery (it kept needing to be pushed for
the phone to turn on when we replaced everything) or if I screwed up the phone entirely. Please help.
TLDR; I tried to flash CWM on a Galaxy S4 and got the "RECOVERY IS NOT SEANDROID ENFORCING" error when trying to boot into recovery. Now the
phone won't get past the S4 logo and I'm not sure if I messed up or if it's the battery's fault.
Any help would be much appreciated. I'd like to thank everyone in advance for looking and for your help.

It's the battery. The "Recovery is not SEAndroid Enforcing" warning appears on all custom recoveries installed on the S4. The warning is simply because the bootloader notices the recovery doesn't have the secure android code in it, so it reminds you of that fact.

Strephon Alkhalikoi said:
It's the battery. The "Recovery is not SEAndroid Enforcing" warning appears on all custom recoveries installed on the S4. The warning is simply because the bootloader notices the recovery doesn't have the secure android code in it, so it reminds you of that fact.
Click to expand...
Click to collapse
Thank you for the reply, Strephon. So I guess the next logical step would be to obtain a new battery? How can I at least be able to get back to the lock screen in this case?

Yes it could be the battery like Strephon Alkhalikoi suggests.
What I also would do is reflash the recovery. But not CWM, try Philz or TWRP.
Make sure to uncheck auto-reboot before flashing.
ps what's the model that you have? You can find the model in the download mode.

Lennyz1988 said:
Yes it could be the battery like Strephon Alkhalikoi suggests.
What I also would do is reflash the recovery. But not CWM, try Philz or TWRP.
Make sure to uncheck auto-reboot before flashing.
ps what's the model that you have? You can find the model in the download mode.
Click to expand...
Click to collapse
Do you mind explaining what the difference between those custom recoveries are? Sorry, I'm new to all this^^;
And I'm not able to access download mode until I get a new battery ^^ Does the model affect flashing custom recovery at all?
Thanks again for the help!