Database Users

[Q] Galaxy S4 SGH-1337 will not boot into recovery mode...

First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.

babrandon said:
First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.
Click to expand...
Click to collapse
having the same exact issues. Ive been trying the past 4 hours on getting it to work.

I think you're both hosed. You can try jtag. Check out mobiletechvideos.com. but call them first and explain what you did. Jtag may not even work.

Mf3 update has new bootloader. No custom recovery options as of now. You can have root but no recovery no flashing.
Sent from my HTC One using xda premium

You lost root because, as you said, you didn't do any research before accepting the OTA update. Now you're about to bork your device trying to flash onto it without, yet again, doing any research. I don't mean to be a hardass but I don't want to see anyone with a brick on this forum. You would be better off with an unrooted stock s4 and just keep your eyes and ears on xda for root/recovery updates for MF3.
Cheers

babrandon said:
First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.
Click to expand...
Click to collapse
I get the same thing as well. You said "I found a fix for this that allows me to reboot my phone into working order". Could you explain how you got this to reboot back to normal? That's all I want at this time too.

l33t_killa said:
I get the same thing as well. You said "I found a fix for this that allows me to reboot my phone into working order". Could you explain how you got this to reboot back to normal? That's all I want at this time too.
Click to expand...
Click to collapse
you just have to go to ur phone download mode by holding volume down and home button and when u get to download mode just simply click on cancel(restart) it will boot ur phone..

mdanish4 said:
you just have to go to ur phone download mode by holding volume down and home button and when u get to download mode just simply click on cancel(restart) it will boot ur phone..
Click to expand...
Click to collapse
Currently, it's sitting on the ATT sphere, white background, with the blue LED light on, got the opening chimes on the reboot as well. Been a couple of minutes now sitting there...
UPDATE
Was able to power it off as it was getting hot, got it plugged into laptop, charging animation is on, with the red LED light on as well. Cooling back down. What do you think now?
UPDATE 2
Did a reboot after charging for a bit, still hanging on the ATT sphere, white background, with the blue LED light on

mdanish4 said:
you just have to go to ur phone download mode by holding volume down and home button and when u get to download mode just simply click on cancel(restart) it will boot ur phone..
Click to expand...
Click to collapse
I am/Was in the EXACT same boat as the OP. I did what was posted above and I was good to go, meaning I can use my phone etc. I have had the phone for 5 days after using an iPhone for 5 years so I am still learning and almost learned the hard way. I will just wait until I can flash ROMs etc.
Thanks for making this thread OP.

babrandon said:
First off, I updated my GS4 OTA to I337UCUAMF3, which I wish I hadn't done. I lost root from it from it because I didn't do my research before accepting the update. I then searched for a way around the update and was able to re-root my phone. When I went to flash CM10 to my phone, it booted into download mode (Odin Mode) with a message in the upper left corner that reads:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
I found a fix for this that allows me to reboot my phone into working order. However, I am no longer able to boot into Recovery Mode, nor am I able to factory wipe my phone. Any time I attempt either of these things, it goes back into the "Could not do normal boot." Odin mode. I tried going back to stock, but it fails every time. I'm sort of new to all of this, obviously, but any help would be appreciated. Everything I have tried has been based on things I've read on XDA, but I guess just because someone posts something doesn't mean you should try it. Lesson learned.
AT&T Samsung Galaxy S4
SGH-I337
Baseband: I337UCUAMF3
Android 4.2.2
Build number: JDQ39.I337UCUAMF3
Kernel version: 3.4.0-812098
[email protected] #1
I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.
Click to expand...
Click to collapse
I'm having the exact same problem. I had read on the forums that people with root were able to install the OTA update no problem. But after I'd installed it this problem came up and there were no solutions in sight

ashkan101 said:
I'm having the exact same problem. I had read on the forums that people with root were able to install the OTA update no problem. But after I'd installed it this problem came up and there were no solutions in sight
Click to expand...
Click to collapse
The solution is in post 7 of this thread...though that will get you able to boot, you will not have a stock (or any) recovery...as trying to install a custom recovery when it's not actually possible is a bad thing!

ashkan101 said:
I'm having the exact same problem. I had read on the forums that people with root were able to install the OTA update no problem. But after I'd installed it this problem came up and there were no solutions in sight
Click to expand...
Click to collapse
Adding myself to this post... Having the same problem.

sincity said:
Adding myself to this post... Having the same problem.
Click to expand...
Click to collapse
Have you tried what was explained in post 7. Boot into download mode and when it gives you the option to continue or cancel, cancel. Others have reported this working.

jd1639 said:
Have you tried what was explained in post 7. Boot into download mode and when it gives you the option to continue or cancel, cancel. Others have reported this working.
Click to expand...
Click to collapse
Yes I did. Actually my situation is a little different. But was hoping to grab info from here too.
What happened: Installed Chainfire3D by accident. Reboot and from that point it got stuck in boot.
Rooted AT&T I337 MF3

sincity said:
Yes I did. Actually my situation is a little different. But was hoping to grab info from here too.
What happened: Installed Chainfire3D by accident. Reboot and from that point it got stuck in boot.
Rooted AT&T I337 MF3
Click to expand...
Click to collapse
Oh, didn't see it was for froyo and Gb only. What firmware do you have?

jd1639 said:
Oh, didn't see it was for froyo and Gb only. What firmware do you have?
Click to expand...
Click to collapse
whatever 4.2.2 is I'm assuming...
My phone was stock... I can't boot into recovery either.

sincity said:
whatever 4.2.2 is I'm assuming...
My phone was stock... I can't boot into recovery either.
Click to expand...
Click to collapse
All of these are 4.2.2, mdb, mdl, mf3. If you have the first two there's hope. If you have the last one, which I'm guessing you do, its no going to be so easy.

jd1639 said:
All of these are 4.2.2, mdb, mdl, mf3. If you have the first two there's hope. If you have the last one, which I'm guessing you do, its no going to be so easy.
Click to expand...
Click to collapse
MF3 - and I'm learning that I might just have to be patient until someone releases a stock/bootloader MF3. Sucks to have this issue.

sincity said:
MF3 - and I'm learning that I might just have to be patient until someone releases a stock/bootloader MF3. Sucks to have this issue.
Click to expand...
Click to collapse
Or perhaps the creeps in charge at AT&T will unlock the bootloader, that would get everyone up and running again. I've done my part to send them messages to that effect...(perhaps I should have not called them creeps, but I can't come up with a nastier term that is able to be printed politely.)

Stuck in download mode SGH-I337 AT&T!! KIES and Odin both fail
Is there a fix yet? I just got my device, successfully had it rooted and then tried installing a custom recovery using goo. It was stupid without research, but it happened.

Set warranty bit message

Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.

reckoner_85 said:
Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
Click to expand...
Click to collapse
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing

Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
haha I will definitely try that.

reckoner_85 said:
haha I will definitely try that.
Click to expand...
Click to collapse
how do u bypass the error? I want to use 4.4

Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
i kinda have the same issue, only i dont have video/audio, and wifi....and ideas?

Help
Hy i have big problem
I try to root Galaxy s4 and all is fine but when i turn on phone he say
"kernel is not seandroid enforcing"
and this is all
Please help me how to fix this
Thanks

martin93612 said:
Hy i have big problem
I try to root Galaxy s4 and all is fine but when i turn on phone he say
"kernel is not seandroid enforcing"
and this is all
Please help me how to fix this
Thanks
Click to expand...
Click to collapse
This appears coz u changed the STOCK kernel. The unique way to solve this is installing STOCK ROM again :good:

Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you

martin93612 said:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
Click to expand...
Click to collapse
Check the Back to Stock link in my signature! Any queries direct to that thread:good:

Thanks finaly my phone working
Thank you :victory:

Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
Laughed loud. Just wanted to let you know.

Please Help! Ive been searching all day yesterday to fix my phone
So i wanted to be updated so i downloaded mf9 and mja and all the kernels or whatever and installed them and was on stock non rooted rom for a while, yesterday i wanted to install sacs custom rom so i downloaded the newest one and flashed via twrp, but now all that happens is i get a message saying "Kernel is not seandroid enforcing" in red "Set warrenty Bit: Kernel" in yellow, I cannot flash anything via odin except philz recovery so i have that on there but i tried to install the stock firmware through odin and everything fails. I even changed usb cords, took out the .md5 extension, plugged the usb cord directly to the motherboard instead of using the front usb which that allowed me to flash philz recovery but i just want a working phone, no rom is working and I cant install any roms please help i need my phone back! Thanks, Chris

Same here :/
chriscolby7 said:
So i wanted to be updated so i downloaded mf9 and mja and all the kernels or whatever and installed them and was on stock non rooted rom for a while, yesterday i wanted to install sacs custom rom so i downloaded the newest one and flashed via twrp, but now all that happens is i get a message saying "Kernel is not seandroid enforcing" in red "Set warrenty Bit: Kernel" in yellow, I cannot flash anything via odin except philz recovery so i have that on there but i tried to install the stock firmware through odin and everything fails. I even changed usb cords, took out the .md5 extension, plugged the usb cord directly to the motherboard instead of using the front usb which that allowed me to flash philz recovery but i just want a working phone, no rom is working and I cant install any roms please help i need my phone back! Thanks, Chris
Click to expand...
Click to collapse
I am having the same issue as you Chris, I'm on the sprint galaxy s4 and i get those same errors and get stuck on a black screen with the blue led illuminated on the top, I can access recovery and download mode. I hope we get some help soon

Stock
Joku1981 said:
This appears coz u changed the STOCK kernel. The unique way to solve this is installing STOCK ROM again :good:
Click to expand...
Click to collapse
But I can't go to recovery/download mode. How can I installing STOCK ROM?
Is there a way to bypass the error?

same problem here. gets stuck at the samsung galaxy s4 spash screen

Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
but gamekiller not working fine..

Here is the Solution
reckoner_85 said:
Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
Click to expand...
Click to collapse
All Right I have the solution for you! I was lucky enough to find someone that knew how to fix this (Damageless) so here is what you need to do.
-Take out the battery and disconnect from computer
-Put battery back in and hold down Vol(down) and home key, then hold power button until it vibrates. Release only the power button after it vibrates.
-You should now be in the download mode, click Vol(up) to continue.
-Download Odin here: odindownload .com
-Download stock ROM here: (dont open click save) sammobile .com and (yes you have to create an account I'm sorry) search for your model number, ex. SM-N900t for tmobile note 3
-install Odin
-check the PDA box not phone and click PDA
-find the stock ROM in your downloads and select that one.
-hit Start and you should be back to normal
It will erase everything you had on your phone which sucks I know but at least your phone works! Good luck! Hope this helps!
Wroclaw7

i have same problem them flash carbon rom and works...

martin93612 said:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
Click to expand...
Click to collapse
You can get all stock firmwares from SamMobile : http://www.sammobile.com/firmwares/
Let me know if you need help with the flashing process.

THANK YOU
THANK YOU THANK YOU I found this post and it restored my phone back to stock!!!!
the only thing I can add to this is use the original cable that came with the phone I was using an aftermarket one and was getting error after error .

[Q] Error message on boot screen after root ?

Hi Guys
Could really use some help here, thought it was about time that I rooted my Note 3, I am using a SM-n9005 and was on 4.3 to start.
I followed some instructions using Odin and CF-autoroot, all went well even had a pass! in the Odin screen but now I am stuck on the loading screen with the following error messages in the left hand corner:
Recovery booting....(in blue)
Recovery is not seandroid enforcing (in red)
Set warranty bit : recovery (in yellow)
Can anyone shed some light on this ? what have I done wrong here and how can I fix it ?
Thank you

colobos said:
Hi Guys
Could really use some help here, thought it was about time that I rooted my Note 3, I am using a SM-n9005 and was on 4.3 to start.
I followed some instructions using Odin and CF-autoroot, all went well even had a pass! in the Odin screen but now I am stuck on the loading screen with the following error messages in the left hand corner:
Recovery booting....(in blue)
Recovery is not seandroid enforcing (in red)
Set warranty bit : recovery (in yellow)
Can anyone shed some light on this ? what have I done wrong here and how can I fix it ?
Thank you
Click to expand...
Click to collapse
I think you used wrong cf autoroot you might downloaded the 4.4 kitkat version

meawww said:
I think you used wrong cf autoroot you might downloaded the 4.4 kitkat version
Click to expand...
Click to collapse
Thank you I managed to figure it out and you was right I was being a bit of a moron .....

Problem Rooting SM-N9005 International 4.3

Hello guys,
i have the following problem:
I have tried rooting my SM-N9005 International version running Android 4.3.But every time i try to flash CF-AutoRoot it reboots and i see the logo of Samsung Galaxy Note 3 SM-N9005 and in the upper left corner on the first line it says RECOVERY BOOTING underneath it says something that there is a error with SEANDROID and underneath it says set version bit:recovery and it's just stucked i flashed back the stock firmware XXUDMJ7.It's there some other way to root my phone or is there something wrong that i do ? i flashed with ODIN 3.07.If you need some other info about my phone i will tell you what you need ! Thank you very much !!

ClimbersTeam said:
Hello guys,
i have the following problem:
I have tried rooting my SM-N9005 International version running Android 4.3.But every time i try to flash CF-AutoRoot it reboots and i see the logo of Samsung Galaxy Note 3 SM-N9005 and in the upper left corner on the first line it says RECOVERY BOOTING underneath it says something that there is a error with SEANDROID and underneath it says set version bit:recovery and it's just stucked i flashed back the stock firmware XXUDMJ7.It's there some other way to root my phone or is there something wrong that i do ? i flashed with ODIN 3.07.If you need some other info about my phone i will tell you what you need ! Thank you very much !!
Click to expand...
Click to collapse
SEandroid line is normal, as for it not working, you can either take the battery out for 30seconds then reboot OR you have used the KK version of CF-Autoroot (latest is Kitkat)

ClimbersTeam said:
Hello guys,
i have the following problem:
I have tried rooting my SM-N9005 International version running Android 4.3.But every time i try to flash CF-AutoRoot it reboots and i see the logo of Samsung Galaxy Note 3 SM-N9005 and in the upper left corner on the first line it says RECOVERY BOOTING underneath it says something that there is a error with SEANDROID and underneath it says set version bit:recovery and it's just stucked i flashed back the stock firmware XXUDMJ7.It's there some other way to root my phone or is there something wrong that i do ? i flashed with ODIN 3.07.If you need some other info about my phone i will tell you what you need ! Thank you very much !!
Click to expand...
Click to collapse
Try odin 1.85

radicalisto said:
SEandroid line is normal, as for it not working, you can either take the battery out for 30seconds then reboot OR you have used the KK version of CF-Autoroot (latest is Kitkat)
Click to expand...
Click to collapse
Yeah you are right i was using the KK version i haven't notice in the thread of Chainfire that there was a download for 4.3 ! Thank you ! Cheers

I got same problem

Please I encountered exactly the same problem yesterday...
I tried rooting with auto root my Samsung note 3 sm-n9005 rebooted and stopped at Samsung logo, displaying
'RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery' at the top...
What do I do... I can't find autoroot for Android 4.3 on chainfire and I don't know where to find the stock rom...
The phone boots to it menu if I reinsert the battery but I still need to root...
pls help...
---------- Post added at 11:23 PM ---------- Previous post was at 11:17 PM ----------
ClimbersTeam said:
Yeah you are right i was using the KK version i haven't notice in the thread of Chainfire that there was a download for 4.3 ! Thank you ! Cheers
Click to expand...
Click to collapse
Pls can you give me the link to the download for 4.3? and do I need to flash stock before trying to root again?

Unable to download new ROM to Note3 N900W8

Hello and I apologise in advance for the size of the post. I'll try to be as succinct as possible but there's a lot to say. First off, I had a Wind Note 3. Then sick of the reception I swapped to Mobilicity. I rooted the phone 8 mos. ago and it went well, but a month later when I tried to install a new rom with Odin I did something wrong. To the best of my abilities, i made sure that what I was installing was for my type of phone. My Note ended up caught in an unending rebooting process with the message 'Recovery Booting...Recovery is not Seandroid Enforcing Set Warranty Bit: recovery'. So I reconnected it to Odin and let it do its thing and I had a mediocre working phone. The menu and back keys were useless. I lived like that until I saw this post. So I downloaded the first item from this site. For Gapps I got the first choice of this list . However when I went to put my mobile in recovery mode it did the same 'Recovery Booting' message as it did the last time. Then I ran Odin again with this and while the phone was still not working properly when I tried to boot on recovery mode it allowed me to. I then uploaded the new rom but I got this message: (please follow this link for pictures.
So I need some guidance in what to do even if it is to tell me to use it as a paperweight. However, I think there's still hope for it. Any input will be much appreciated it.

I suggest you start over by flashing a stock rom from sammobile.com.

Update
audit13 said:
I suggest you start over by flashing a stock rom from sammobile.com.
Click to expand...
Click to collapse
I did found the rom as u advised. The problem still persist, Odin shows no button called PDA as a mention but AP instead. Any ideas?
Sorry for pestering you, I dont mean to spam you. Thank you kindly,
PW

AP=PDA
Sent from my SM-G925F

PDA appears in Odin 3.07. AP appears in newer versions.