Database Users

Phone won't boot past "Galaxy S4" splash screen

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

I goofed, and I don't know how I did it

Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...

Think I figured it out
Well after writing this, for my own personal sense of masochism and an overall morbid curiosity, I kept reading, and figured out how to get the phone to actually boot into proper recovery mode (as in NOT Odin), and was able to get a ROM back on the phone, as I didn't care for any of the nandroids I had there. As I am not sure that anyone actually viewed this before I resolved my own issue much less had a chance to respond, it's not appropriate to thank anyone for solving my own problem, except for the poster of the thing that I read which led to my resolution, but I will throw out a blanket thank you to all those that take the time to develop, write, and help others solve the stupid stuff, it is appreciated, at least by this Ohioan, who sometimes manages to get in over his head!
dsly4425 said:
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Click to expand...
Click to collapse

[Q] GAPPS screw up my s4

Hi,
i have serious problems with my S4(i9505):
I rooted it when i got it and have installed various roms so far. The last working one was "liquid smooth".
Then it begann to reboot from time to time and when the problems got worse i decided to reinstall again... now, i think my problems arrived with the 4.4 roms. I installed pacman and tried to boot, it didn't work and i think that's when my bootup sequence changed, now i have a little text in the corner saying "kernel is not seandroid enforcing. Set warranty bit : kernel"
so i thought something must be wrong with the kernel and installed various kernels, hoping to clear that message in the corner. At some point i realized that this only makes my situation worse (s4 reboots directly after booting, while bootin, while finishing up "first boot", it gets stuck in bootloops, etc).
Right now i'm not even sure if i understand the whole concept of kernels and roms anymore... so i decided to ignore the message for now and focus on getting my phone to work... i installed some roms again, some (i think the 4.2'S) seem to work, the 4.3's all crash while booting...
i managed to get liquid smooth back on it again (2.9).
Oh and i tried reinstalling stock kernel but the installation under CWM aborted.
Now i can use basic phone options again, but as soon as i flash gapps(no matter on which rom (Cyanogen, pacman, liquid smooth), the phone won't boot anymore, i re-downloaded the package several times, it's the latest one, so it should be okay...
S4 google edition of course doesn't work at all ...
Anyone an idea, how i can get google apps back ? Or basically just get my phone to work ?
Furthermore : How do i clear the message (kernel is not seandroid enforcing)? My basic goal is to have a working android 4.3 enviroment with gapps...can't be that hard ...
i spent the whole day on that, i have used searchfunction not only on this forum, so sorry if i have missed a thread stating the same problem. Plus: i need someone to talk to
EDIT:
I've installed Stock ROM, now it keeps rebooting at the point where i can set up wlan ...

Black screen and "System UI has stopped working" error with XCover 2

So, I'm a total noob with the android phones. Just bought my Xcover 2 after using my old C7 for 3-years. I got curious about the rooting and decided to go on with it. Installed CWM just fine and rooted the phone successfully. Then I decided to try flashing the S4 Accuweather widget right away (I didn't like the stock one at all and I had a trend plus for few weeks which had the S4 widget).
That didn't go so well... I got the "System UI has stopped working error" popping up all the time. Decided to go back to recovery and try another S4 widget install. Didn't work either. Then I decided that doing a "data wipe" would be a good idea. But nope instead I get the same "System UI has stopped working" and a black screen with no apps and no way to access the apps. I was really idiotic to not make backup of my current ROM state before starting to install anything. I just thought that "it's just one small app".
Now I'm currently downloading the stock ROM from Samsung Updates and trying to flash it through Odin. Will that restore my phone back the the original state or am I just simply ******? Gosh, I wish I had never done the rooting, I was fine with the original....

Hi
Yes, Flashing the proper stock firmware should get you back in business.
Some tips going forward...
Don't install or flash anything not made for your exact device, unless you find confirmation that it will work. You could have many issues, including bricking your device.
And, a factory reset won't fix system issues, it will only wipe your cache and data partitions. So system changes, like what you attempted will not be fixed.
And other issues or questions for your device can be asked here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!

[Q] Help needed with potentially bricked S4 LTE

Hi All,
I hope I'm posting in the right place, apologies if not.
I have been running Cyanogenmod on my S4 i9505 since Christmas. A couple of weeks ago, for no apparent reason, the phone started switching itself off so I decided to try and flash back to a stock ROM using Odin and the most recent firmware (5.0.1) from sammobile.com. I'm pretty new to this and don't have much in depth knowledge at all - hence opting for the apparently easy Cyanogenmod rooting option in the first place. The Odin flash 'passed' yet on reboot I got stuck at the Samsung logo and the phone then gets stuck in a boot loop if I switch it off using the power button. I then tried to flash an older firmware (4.2.2) but it has failed twice, leaving me with a 'brick'.
As I said, my technicial knowledge here is very limited but any step by step help to trying to get the phone back up and running would be greatly appreciated. Have I completely ruined the phone past repair, or is there a way round this?
Many thanks in advance

Whenever you upgrade to Android 5.0.1 from an earlier version it takes up to twenty minutes before it fully boots. This is because of the internal change from the Dalvik app compiler to the new ART compiler Android now uses. Android apps come in multiple parts, and on old versions of Android these parts were assembled into a single running image every time you ran the app. This is called "Just In Time" (JIT) compiling. The new ART compiler uses "Ahead Of Time" (AOT) compiling. It assembles all the apps once, rather than repeatedly assembling an app when you run it.
When you upgrade to Android 5.x and future versions of Android, Android will need to spend time compiling every single app on the device before it fully boots. This can take quite a while if you have a lot of apps, and an unfortunate side effect of this is that the device looks like it's stuck in a bootloop.
If you're able to get into Download Mode, your S4 isn't bricked. Install 5.0.1 again, but this time don't touch the device for a while.

Many thanks, a little patience was all that was needed. Re-flashed 5.0.1 and waited for first boot - all sorted!