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

Search This thread

chrispysaid

Member
Feb 22, 2010
8
1
The Important point is the order:
Vol up then Home Then Power and after all that when u see the saumsung logo jus RELEASE THE POWER BUTTON!
hope i have helped...

No, you haven't really helped. Order isn't a factor here, the phone returns to Download Mode with the message "Could not do normal boot" even after following proper procedure for Recovery Mode. I think the recovery is either inaccessible or broken due to attempted flashing of custom recovery over a completely unwritable one.
 
  • Like
Reactions: Sina Irvani

John The Rhino

Senior Member
Dec 25, 2013
211
130
I used Rom Manager to flash CWM, that took me to stock recovery every time. Then I tried TWRP using Goo. That actually caused my phone to fail boot, and go into Download mode. Flashing with Odin failed every time, but the Boot Into Download Mode, Cancel workaround worked to at least get my phone back into working order.

The fact that I started on MK2 rather than MF3 - does that make a difference? Do I have more options here? Odin still seems unresponsive...

It would be best if you slowed down, took your time to do some research. Then you would know that you can NOT flash any custom recovery to mk2 build other than Hashcode's Safestrap. version 3.71. Nothing else will work. IF your phone is really messed up you can now Odin back to stock as we now have FULL tar files available.

Please Read the following it will help you.

http://xdaforums.com/showthread.php?t=2616221
 

bling8d

Member
Feb 7, 2011
25
0
Did you buy that s4 from someone? I did and I have the same issue. The phone is actually a fake. A well done clone... Google your build number to check. I just lost 200$ : (
 

saheb.singh

New member
Jan 24, 2014
3
0
same issue

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
se.infra@SEP-103 #1

I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.

i am having exack same issue any luck with formatting your phone
 

ttt3008

Member
Jan 8, 2013
30
18
Hawaii
A beautiful brick.

i am having exack same issue any luck with formatting your phone


I just went out to get a Nexus 5 because of this same issue. I tried everything i could to get the phone to update or factory reset.
I guess the only solution to this is to be careful of what carriers you buy your phones from. Now i have a beautiful brick sitting on my desktop that's stuck on 4.2.2. What a waste. :(
 

jd1639

Inactive Recognized Contributor
Sep 21, 2012
16,833
5,404
Minnesota
I just went out to get a Nexus 5 because of this same issue. I tried everything i could to get the phone to update or factory reset.
I guess the only solution to this is to be careful of what carriers you buy your phones from. Now i have a beautiful brick sitting on my desktop that's stuck on 4.2.2. What a waste. :(

First, the nexus 5 is a nice device, you'll be happy with it. It's what I'm writing this post on. On the s4, did you try to Odin the stock mf3 firmware?
 
  • Like
Reactions: ttt3008

ttt3008

Member
Jan 8, 2013
30
18
Hawaii
GOT IT!

First, the nexus 5 is a nice device, you'll be happy with it. It's what I'm writing this post on. On the s4, did you try to Odin the stock mf3 firmware?

Thanks for the help I just found the solution here http://xdaforums.com/showthread.php?t=2504311 . I guess i will safestrap it up and see what happens from there. I still think ill be set on my Nexus 5 though. :eek:

Thanks Again!

Nice.jpg
 

Attachments

  • Nice.jpg
    Nice.jpg
    153.8 KB · Views: 497

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    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.

    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..
    1
    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
    se.infra@SEP-103 #1

    I can try my best to provide any further information that may assist you in assisting me! Just ask. Thanks in advance.

    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.
    1
    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..

    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
    1
    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..

    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.
    1
    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.

    Read this...

    http://xdaforums.com/showthread.php?t=2360859