Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.
Related
So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!
Try a different kernel, also, pull the battery for 5 min, it will boot.
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash
id try odin
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//
Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.
fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up
fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.
samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok
fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear
What I want to do is install a stock non rooted rom, kernel, and recovery. I am not sure how to change recovery to stock either is it like flashing a rom? Please give me some links for these I can't seem to find them, besides the stock kernel I found that.
----------------------------------------------------------------------------------The reason I want the above is bellow, if it matters.-----------------------------------------------------
My phone is about 95% broken.
Before, every rom/kernel combination would randomly restart, it was my phone it self I believe.
I went to a stock rooted rom, but then it restarted, and my lock screen worked, yet my home screen was black all i could do was slide my status bar down.
After that i restarted my self and then it got stock forever on the screen where it says Samsung galaxy s4.
The 5% working part is my recovery, for the most part.
I keep having to do a full wipe, not just system wipe otherwise it says error unable to mount preload or i/o or a few other things, I have to system wipe before every rom attempt.
I tried several popular roms such as sacs and triforce and a few other roms and all the kernels also.
The phone will turn on, work for a little normally, then crash again and go into the infinite loading screen where is simply says galaxy s4.
This phone is only 3 months old, so I want to take it back to sprint being completely stock so they give me a new phone.
I need links to files I need, and if i am forgetting to change anything back to stock please let me know. Thank you.
I replied to you in the newbie thread, but to return to complete stock download the latest firmware from here: http://www.sammobile.com/firmwares/ and install it with odin. Do a factory reset before and after install to make sure you have cleared out what ever is causing your problems. After this process you will be completely stock and unrooted. If you are still having problems after this it is probably hardware related.
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
RawSynergy said:
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
Click to expand...
Click to collapse
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
DeadlySin9 said:
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
Click to expand...
Click to collapse
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
RawSynergy said:
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
Click to expand...
Click to collapse
NB1 is the only one you can get, just try downloading either one again.
DeadlySin9 said:
NB1 is the only one you can get, just try downloading either one again.
Click to expand...
Click to collapse
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
RawSynergy said:
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
Click to expand...
Click to collapse
When you plug in the phone in Download Mode, does the blue box in Odin light up? If not, reinstall samsung drivers
Sent from my SM-N910G using Tapatalk
Hi Guys,
Not sure if I boogered something up, or if I'm having an actual hardware issue. All my important stuff is backed-up elsewhere, so not worried about whats on the phone right now, just need to get it up and running again.
I have Philz 6.41.6, and CWM 6.0.4.8. I can get into recovery, and I can get into download mode no problem. Phone will connect with Odin, and I can flash apparently flash without issue. Do have an EFS backup as well.
When I restore a known-good cwm backup, or attempt to install a new ROM (been using xXx ROM with no issue prior), the OS will boot up, but the screen will occasionally flicker, or blackout and not come back. Side buttons respond (vibration). It comes back sometimes, but lags quite a bit. I get a constant "No Service", and it never connects. I can press the home button, but the menu/back buttons just flash.
Tried flashing BL and modem via this thread: http://forum.xda-developers.com/showpost.php?p=52210611 , just to make sure they were good, but no change in behavior.
Read through several topics... Not sure what to try next...
Should I attempt to flash back to stock? Or? I'm comfortable installing, editing, flashing, etc, did it a long time with my old Atrix. Still new to the S5 though, its a bit of a different animal.
I sure would appreciate any suggestions, advice, or instruction.
Thanks All,
Keto
I would definitely try flashing a pure stock ROM thru Odin just to make sure it's not a software issue. Though the issues you describe sound ominous...
Flash stock from sammobile, boot into stock recovery, factory reset
See if it behaves itself after that and go from there
Thanks guys.
I flashed the stock ROM, and did a factory reset. Still misbehaving. I noticed the phone getting pretty darn warm on the back, so, shut it down for a while. When cooled down, it behaves quite well, BUT soon as I load it with anything 'intensive' for a little while, it gets hot. and starts wig'n out again.
Seems like there are some hardware issues, unless you guys have other ideas?
Use KIES and go to Tools > Emergency firmware recovery.
Give it a try
i have been trying to install a good rom on my s5. i know that since i have an 11' toshiba chip, i cant do any major custom roms only stock touchwiz roms. i have 3 or 4 that i have found that actually work on my phone and when i tried a new rom today, it didn't work. so i flashed 4.4.2 again to start from scratch and i went back to my usual stock deodexed rom that is always a for sure rom that works. today when i flashed it, twrp (safestrap) prompts me to either boot normally or to continue. i have had this problem in the past, and whenever it shows that screen, it will never boot up, after the prompt it will just have a black screen for about 5 min. before booting stock recovery. if i boot it up again, safestrap will still prompt me if i want to boot recovery or continue and keep repeating this cycle. last time, it had resolved itself and didnt show up after wiping and reflashing my rom. this time it wont go away and my phone wont boot anything. thanks in advance
as.hs said:
i have been trying to install a good rom on my s5. i know that since i have an 11' toshiba chip, i cant do any major custom roms only stock touchwiz roms. i have 3 or 4 that i have found that actually work on my phone and when i tried a new rom today, it didn't work. so i flashed 4.4.2 again to start from scratch and i went back to my usual stock deodexed rom that is always a for sure rom that works. today when i flashed it, twrp (safestrap) prompts me to either boot normally or to continue. i have had this problem in the past, and whenever it shows that screen, it will never boot up, after the prompt it will just have a black screen for about 5 min. before booting stock recovery. if i boot it up again, safestrap will still prompt me if i want to boot recovery or continue and keep repeating this cycle. last time, it had resolved itself and didnt show up after wiping and reflashing my rom. this time it wont go away and my phone wont boot anything. thanks in advance
Click to expand...
Click to collapse
Find youre phones firmware and put phone into download mode and flash firmware!