[Q] Galaxy S4 SGH-1337 will not boot into recovery mode... - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

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.

Related

[Q] Bricked my At&t galaxy s iii

So, I tried to root my phone using instructions here
http://forum.xda-developers.com/showthread.php?t=1703488
I skimmed it the first time and missed the red, bold text saying not to use this on the US version and I also did not perform a backup, but thats in the past. Currently, it will boot, give me the Samsung logo and shutdown.
I'm sure this is wrong, so I hope someone can correct me.
-First, I need to find the correct rom(which I've been unable to do so far)
-I boot the phone into download mode(Vol down+home+power?) and plug it into my pc
-I open Odin, select the new rom as the pdf file, and press start.
Also, if I manage to screw this up again, would at&t be willing to help since its not totally bricked?
anonymous78 said:
So, I tried to root my phone using instructions here
http://forum.xda-developers.com/showthread.php?t=1703488
I skimmed it the first time and missed the red, bold text saying not to use this on the US version and I also did not perform a backup, but thats in the past. Currently, it will boot, give me the Samsung logo and shutdown.
I'm sure this is wrong, so I hope someone can correct me.
-First, I need to find the correct rom(which I've been unable to do so far)
-I boot the phone into download mode(Vol down+home+power?) and plug it into my pc
-I open Odin, select the new rom as the pdf file, and press start.
Also, if I manage to screw this up again, would at&t be willing to help since its not totally bricked?
Click to expand...
Click to collapse
Yes, this is correct. I would recommend looking on Sammobile and see if you can find a stock version for your phone model. You use the PDA file in ODIN, then you flash.
As for AT&T, I am not sure of their policy regarding software crashes on phones.
NightSkylar said:
Yes, this is correct. I would recommend looking on Sammobile and see if you can find a stock version for your phone model. You use the PDA file in ODIN, then you flash.
As for AT&T, I am not sure of their policy regarding software crashes on phones.
Click to expand...
Click to collapse
I looked last night and I didn't see it (sgh-i747 right?). Some guides use a PIT file in odin as well, will I need this and where would I find it? If I can't get the stock rom are there any compatible custom ones you'd recommend?
anonymous78 said:
I looked last night and I didn't see it (sgh-i747 right?). Some guides use a PIT file in odin as well, will I need this and where would I find it? If I can't get the stock rom are there any compatible custom ones you'd recommend?
Click to expand...
Click to collapse
Its rare that you would have to use a PIT File, mostly for the fact that it can mess up the bootloader.
As you have performed a soft brick, you likely do not have CWM, thus you cannot flash any custom firmware. *
My advice would be to wait to see if someone will upload the stock firmware for your model. I would also visit AT&T and say that your phone suffered a software crash.
:good:
* However, it is possible to flash a custom ROM if they can be flashed VIA ODIN, such as the CM9 Resurrection edition. (Does not exist for the AT&T Edition just yet)
I considered going into the store and playing dumb, but I heard they just replace the phone on the spot and sometimes later check the bricked phone before fixing it. I don't want to risk receiving a $600 bill in two weeks.
Can they tell the difference in my case?
I doubt it, as they are not trained as samsung tech support is.
Go into download mode, at the top corner, you will see
Produit name:
Custom Binary download:
Current Binary:
System Status:
Can you tell me what those are on your device?
NightSkylar said:
I doubt it, as they are not trained as samsung tech support is.
Go into download mode, at the top corner, you will see
Produit name:
Custom Binary download:
Current Binary:
System Status:
Can you tell me what those are on your device?
Click to expand...
Click to collapse
Product name: SGH-I747
Custom Binary download: yes(3 counts)
Current Binary: Custom
System Status: Official
In this case, as it is a custom Binary, it would most likely void your warranty. However, if they do not know how to check, then you should be good
So I went down to the at&t store and they couldn't do anything without sending it to tech or having them come in or something. She also said that if the warranty is void they won't do anything, not even for a fee.
I suppose I'll have to activate my old phone until the rom is released.
I'm sorry to hear that mate, but no worries, it wont be long till someone post's the official stock firmware
I hope you had taken a efs backup before this blunder.
Sent from my GT-I9300 using XDA
Man, I feel for you but just got to be patient with things like this. You're performing something that can and will damage your phone if you don't read the directions.
Sent from my GT-I9300 using xda app-developers app

[Q] Reset Samsung Galaxy S4 I9505

Hey,
I have following problem:
Few days ago I bought a Samsung Galaxy S4 Lte (I9505 jfltexx). I wanted to root it and then flash CM onto it.
Rooting went fine but when I flashed CM it aborted with Error 7. After that it was soft bricked but i managed to flash the Stock Rom back and everything was fine again.
But today I tried it again but got following problem. CWM was gone and i had to reflash it. But then everytime I tried to get into recovery mode the phone freezed at the "Samsung Galaxy S4 I9505" Logo with the little blue "recovery booting" in the left upper corner. I tried to flash CWM and also twr but it did not help.
SO my final thought was flashing the stock rom again to at least have a working phone. But when I tried to flash the Stock Rom ODIN failed and my phone gave this error "SW REV. CHECK FAIL : fused:2, Binary: 1".
Then every time it started it booted into download mode and said "firmware upgrade encountered an issue. please select recovery mode in kies & try again". I googled how I can solve this and someone said that it has something to do with root. So again I flashed the CF auto root and thank god it booted up normally.
But now my problem: I have no root on my phone(superSu says that there are no SU-binarys), I can't update my stock-firmware because the software update says that my phone has been changed. What can I do to 1. gain root access again 2. flash a custom rom(best would be SlimBean)?
Hope you can help me
lup3x said:
Hey,
I have following problem:
Few days ago I bought a Samsung Galaxy S4 Lte (I9505 jfltexx). I wanted to root it and then flash CM onto it.
Rooting went fine but when I flashed CM it aborted with Error 7. After that it was soft bricked but i managed to flash the Stock Rom back and everything was fine again.
But today I tried it again but got following problem. CWM was gone and i had to reflash it. But then everytime I tried to get into recovery mode the phone freezed at the "Samsung Galaxy S4 I9505" Logo with the little blue "recovery booting" in the left upper corner. I tried to flash CWM and also twr but it did not help.
SO my final thought was flashing the stock rom again to at least have a working phone. But when I tried to flash the Stock Rom ODIN failed and my phone gave this error "SW REV. CHECK FAIL : fused:2, Binary: 1".
Then every time it started it booted into download mode and said "firmware upgrade encountered an issue. please select recovery mode in kies & try again". I googled how I can solve this and someone said that it has something to do with root. So again I flashed the CF auto root and thank god it booted up normally.
But now my problem: I have no root on my phone(superSu says that there are no SU-binarys), I can't update my stock-firmware because the software update says that my phone has been changed. What can I do to 1. gain root access again 2. flash a custom rom(best would be SlimBean)?
Hope you can help me
Click to expand...
Click to collapse
mate mine says the same as yours. so might just be because it failed not sure tho we will just have to wait and see if someone can come up with a answer. regards
joecool666 said:
mate mine says the same as yours. so might just be because it failed not sure tho we will just have to wait and see if someone can come up with a answer. regards
Click to expand...
Click to collapse
thank god somebody with the same problem! Is your device rooted? because whenever i try to root it odin says pass and SuperSu is installed but the phone is not rooted
lup3x said:
thank god somebody with the same problem! Is your device rooted? because whenever i try to root it odin says pass and SuperSu is installed but the phone is not rooted
Click to expand...
Click to collapse
not now its not. going to wait for c-f for fix until then i am staying where i am stock unrooted lol just to be safe.
joecool666 said:
not now its not. going to wait for c-f for fix until then i am staying where i am stock unrooted lol just to be safe.
Click to expand...
Click to collapse
GOTCHA! I used the auto root from here https://plus.google.com/+Chainfire/posts/5ggu7naWtaW and it finally worked! I don't know if it will work for u but i tried it out and i finally got it. Now to the ROM Part
What is this great advantage that rooting and installing cf brings, that makes you run the risk of destroying your brand new, very expensive phone?
YIKES1412 said:
What is this great advantage that rooting and installing cf brings, that makes you run the risk of destroying your brand new, very expensive phone?
Click to expand...
Click to collapse
The fact that i really don't like this mess which samsung calls a firmware. When i buy a pc i want to do anything i want with it. Same goes for smartphones.
lup3x said:
The fact that i really don't like this mess which samsung calls a firmware. When i buy a pc i want to do anything i want with it. Same goes for smartphones.
Click to expand...
Click to collapse
Ok, I'm just wandering what big difference it makes. What extra does it enable your phone to do? I mean it must be really good to run this risk.
Sent from my GT-I9505 using xda app-developers app
YIKES1412 said:
Ok, I'm just wandering what big difference it makes. What extra does it enable your phone to do? I mean it must be really good to run this risk.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
First of all it's the principle that I don't want to have a phone where Samsung tells me what to do and what not. Then there are things like root which are necessary for me because I'm also using it to test my apps which require root access. And also of course apps from the play store which need it. I'm currently using Slimbean because there's no AOKP build for the I9505. It requires less space on the phone, it's heavily customizable and it has the look of vanilla android. And a huge portion of why I am doing this is just me being curious about such things.
In the end it worked and I learned very much new stuff.
Sry 4 bad english
Hey your English is very good mate. And I was just curious as to why you run the risk, thanks for explaining it to me. I rooted and put a new rom onto an orange san francisco (zte blade) once. But that was not an expensive phone. My wife would kill me if I messed up this s4 with almost 2 years of contract to go lol

[Q] Firmware Upgrade Encountered an Issue

My sgh-i337 was stuck in a bootloop where twrp wasn't working, but using Odin didn't work either. What I ended up doing was upgrading the firmware in Kies, which worked, but it stayed on mdl firmware. It completely wiped my system. No data whatsoever (except my external sd card) and no root. I stupidly upgraded to mf3, because I didn't know that AT&T had locked down the bootloader. When I realized this, I went straight back to Kies and tried to do the upgrade again, but I didn't realize that it was solely for mdl. So my phone got stuck in "Firmware upgrade an issue. Please select recovery mode in Kies & try again." There is a yellow caution sign in the middle, with two dots going to the left with a phone at the end, and two dots to the right of the sign with a computer at the end. In the upper left-hand corner, there is the Odin Mode dialogue:
"ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
The only thing I can boot to other than the above mode is Odin Mode, but because my phone is no longer rooted, this does me no good. I can't boot to recovery mode, either. When the phone is off (from taking the battery out or holding the power button), by pressing the power button, it goes to the firmware upgrade issue screen. In another thread, it mentioned booting to the confirmation to boot to Odin, and pressing the volume down button to restart, but this takes me right back to the firmware upgrade issue screen.
Please help me!!!!!
P.S. Someone mentioned taking it to the AT&T retailer because it is no longer rooted, but I want to see if I can avoid this because the warranty might be voided because it was rooted.
You'll have to flash the mf3 firmware now. Use Odin. Google mf3 tar files xda
jd1639 said:
You'll have to flash the mf3 firmware now. Use Odin. Google mf3 tar files xda
Click to expand...
Click to collapse
Odin doesn't work because it is no longer rooted. Thanks for the reply though.
txk623 said:
Odin doesn't work because it is no longer rooted. Thanks for the reply though.
Click to expand...
Click to collapse
You don't need to be rooted to use odin
jd1639 said:
You don't need to be rooted to use odin
Click to expand...
Click to collapse
Thanks a lot.
I added MF3.tar mirror on my thread http://forum.xda-developers.com/showthread.php?t=2573080 . And u don't need to be root to use Odin..... if u would like to upgrade to 4.3 mk2 this thread might also help you .......goodluck.....
SWYPED_FROM_S4_MF3_REDVENOM

[Q] New To Android

Hi all,
I recently switched over from apple to Android, it was all going really well until recently my phone soft bricked....
Ill try and be as detailed as i can, and respond as quickly as possible.
The phone specs
Canadian 16gb Samsung galaxy s4, Telus.
The phone boots and sticks at the Samsung Galaxy S4 screen.
I cant access the recovery mode.
I can access Odin.
I would love to get the phone rooted and maybe a mod on it, but as of right now its incapable of doing anything, ive read around the forums for the past 2 nights on how to fix the phone but all have come up fairly dry.
Would love some fresh input and help
Thanks Guys and Gals!
Scott
sdawg1010 said:
Hi all,
I recently switched over from apple to Android, it was all going really well until recently my phone soft bricked....
Ill try and be as detailed as i can, and respond as quickly as possible.
The phone specs
Canadian 16gb Samsung galaxy s4, Telus.
The phone boots and sticks at the Samsung Galaxy S4 screen.
I cant access the recovery mode.
I can access Odin.
I would love to get the phone rooted and maybe a mod on it, but as of right now its incapable of doing anything, ive read around the forums for the past 2 nights on how to fix the phone but all have come up fairly dry.
Would love some fresh input and help
Thanks Guys and Gals!
Scott
Click to expand...
Click to collapse
Flash a stock .tar with ODIN, and start over
L Chupacabra said:
Flash a stock .tar with ODIN, and start over
Click to expand...
Click to collapse
Is there any reliable soures for a stock .tar...
Also I cant get the phone to access recovery.
" Kernal is not seandriod enforcing"
"Set warranty bit: Kernel"
Thanks again.
sdawg1010 said:
Is there any reliable soures for a stock .tar...
Also I cant get the phone to access recovery.
" Kernal is not seandriod enforcing"
"Set warranty bit: Kernel"
Thanks again.
Click to expand...
Click to collapse
Bump*
sdawg1010 said:
Bump*
Click to expand...
Click to collapse
Goto sammobile download for i337m, they are all Bell based but they will get you going. Make sure you download the right one, 4.3 or 4.4 if you took the update before you started messing around. You say you can't get into recovery, would be helpful to know what it was you were trying to do to get here....
Gage_Hero said:
Goto sammobile download for i337m, they are all Bell based but they will get you going. Make sure you download the right one, 4.3 or 4.4 if you took the update before you started messing around. You say you can't get into recovery, would be helpful to know what it was you were trying to do to get here....
Click to expand...
Click to collapse
Thank you, and it was on 4.3, and the phone would randomly restart itself, that started probably a week ago, and then it started doing it more often till it got to the point where, i was like screw it, ill factory reset, and after the factory reset, it has appeared to get stuck in a bootloop, but the bootloop wont allow me to enter recovery mode either...
Ive been through multiple tutorials and what not on how to access the recovery, i had accessed the recovery before it stopped allowing access to it.
Very frustrating..but thanks for a pointer in the right direction.
Scott

AT&T Galaxy S4 Recovery fails at 24%

My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.
StephenTiz said:
My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.
Click to expand...
Click to collapse
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.
No recovery options
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
No recovery options
sway8966 said:
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.
Click to expand...
Click to collapse
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
StephenTiz said:
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
Click to expand...
Click to collapse
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.
Woop Woop!
sway8966 said:
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.
Click to expand...
Click to collapse
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.
StephenTiz said:
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.
Click to expand...
Click to collapse
I am glad that it works out for you.
Rooting is so easy from that point. Just get towel root and root it. The link also included in my previous post. After the root you might need to disable the AT&T OTA update too. The instructions are also in that post too.

Categories

Resources