Post Reply

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

OP babrandon

15th August 2013, 10:57 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Aug 2013
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.
15th August 2013, 10:59 PM   |  #2  
dankify's Avatar
Member
Flag San Angelo
Thanks Meter: 3
 
51 posts
Join Date:Joined: Aug 2013
More
Quote:
Originally Posted by babrandon

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.


having the same exact issues. Ive been trying the past 4 hours on getting it to work.
16th August 2013, 12:25 AM   |  #3  
jd1639's Avatar
Recognized Contributor
Minnetonka, MN
Thanks Meter: 3,527
 
10,228 posts
Join Date:Joined: Sep 2012
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.
16th August 2013, 12:41 AM   |  #4  
bhp090808's Avatar
Senior Member
Flag Sebring
Thanks Meter: 670
 
470 posts
Join Date:Joined: Jan 2012
Donate to Me
More
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
16th August 2013, 12:50 AM   |  #5  
xBeerdroiDx's Avatar
Senior Member
Flag Fort Worth
Thanks Meter: 1,418
 
2,321 posts
Join Date:Joined: Nov 2012
More
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
20th August 2013, 05:13 AM   |  #6  
Junior Member
Thanks Meter: 2
 
14 posts
Join Date:Joined: Aug 2013
More
Quote:
Originally Posted by babrandon

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.
Last edited by l33t_killa; 20th August 2013 at 05:17 AM. Reason: edit subscribe
The Following User Says Thank You to l33t_killa For This Useful Post: [ View ]
20th August 2013, 05:23 AM   |  #7  
mdanish4's Avatar
Senior Member
Miami, Florida USA
Thanks Meter: 10
 
149 posts
Join Date:Joined: Apr 2009
More
Quote:
Originally Posted by l33t_killa

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..
The Following 2 Users Say Thank You to mdanish4 For This Useful Post: [ View ]
20th August 2013, 05:46 AM   |  #8  
Junior Member
Thanks Meter: 2
 
14 posts
Join Date:Joined: Aug 2013
More
Quote:
Originally Posted by mdanish4

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
Last edited by l33t_killa; 20th August 2013 at 06:32 AM.
The Following User Says Thank You to l33t_killa For This Useful Post: [ View ]
21st August 2013, 01:31 AM   |  #9  
Junior Member
Thanks Meter: 1
 
5 posts
Join Date:Joined: Aug 2013
Quote:
Originally Posted by mdanish4

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.
The Following User Says Thank You to mdbsat For This Useful Post: [ View ]
25th August 2013, 03:21 AM   |  #10  
Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Aug 2010
Quote:
Originally Posted by babrandon

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'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

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes