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
Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
JJ2013 said:
Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
Click to expand...
Click to collapse
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Further details of whats been tried
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Yes, I neglected to include that I tried wiping cache first, then re-boot attempt, then cleared cache and factory reset, then tried to boot, then wiped cache and factory reset followed by CWM recovery then boot attempt, then cleared cache, re-boot attempt, then all over again and flashed stock - all with no change - boot loop prevailed. What troubles me is that with no other changes the phone froze and re-booted on stock firmware?? And weirder still that once it re-booted the first time it stayed alive for 5 minutes, then 2 minutes, then less than 1, to 'that's all folks' and continued to decrease how far it even went in boot attempt. To the 'slightly informed' like me that seems strange - that's why I was wondering if it could be a hardware failure causing ROM or RAM to be corrupted further with each boot attempt - or - with time 'on'.??
Will try one click mf9 and post back
rimgarciag said:
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
JJ2013 said:
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
Click to expand...
Click to collapse
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Very wise advise
ROMANTiC KiD said:
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
The title say's it all - but this is very wise advise for us all! Electronics can suffer from infant mortality issue's, and I would agree 101% with you!
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
No to 4.3
BIGSAMDA1ST said:
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
I am actually sure it was on 4.2.2 the day it died - still had the notification nag that update was downloaded. I was going to look for how to remove that 'nagging' notification but hadn't yet. Since I rooted the day I got it and installed CWM any OTA update (4.3) should have failed even 'if' I accidently hit the 'system update downloaded' prompt on my notifications screen, which I didn't. The phone had been on for about 4 hours when it first locked and re-booted while texting - and had it updated it would have had to re-boot which I think I would have heard/seen/witnessed some kind of evidence that it had. I think you are going in a good direction though, looking at all possibilities. I know from root checker it rooted successfully and since I made a CWM backup I know stock recovery was gone - so very unlikely 4.3 found it's way in.
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Will try removing SD card
cruise350 said:
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
No, I only installed but never opened or set up folder mount so that never even crossed my mind. I just got home and have a few things to try - and I think the first and simplest is removing the SD card! OK, tried that to no avail - boot loop get's to samsung logo and repeats. Tried to clear cache and factory reset with card removed and tried again after battery removal for 2 minutes. Same situation - nothing has changed. Will try 1 step restore next. Downloaded on my laptop but had to leave that with a co-worker for data aquisition project - have to download again here at home.
This is off track, but I have never asked for help and//or participated in a forum like this before. I am happily suprised by the intelligent, thoughtful responses I have recieved so far. Didn't expect anything, but am glad I asked - and even though I am still 'stuck' I have had incredibly good input into potential resolutions for this issue. Thank you all for the assistance so far
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Verified through download mode - no Knox line present
cruise350 said:
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
No luck - bricked or dead phone...
JJ2013 said:
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
Click to expand...
Click to collapse
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
JJ2013 said:
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
Click to expand...
Click to collapse
I haven't tried this and not sure of the possibility of it working but if you could establish a connection via fastboot or download mode to a computer running adb you could be able to pull the log from dev/log/ and see exactly what is going wrong.
Look here http://stackoverflow.com/questions/12995030/how-to-use-adb-pull-command for info on pulling files in adb
Sent from my SPH-L720 using XDA Premium 4 mobile app
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
HELP
JJ2013 said:
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
mndbtt said:
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
Click to expand...
Click to collapse
No garantee, but I had rooted mine before it went haywire and bootlooped. When I took it in they had the phone for 15 minutes in the back out of my site - expect they went into download mode and could see it was not original (rooted) but replaced it anyway without any fanfare. BTW, after 3 weeks with the new device I rooted it as before - this time using TWRP becouse I had recently helped a friend root a tablet and used TWRP recovery - liked it so... In any case, I have had my rooted S4 (#2) running without issue ever since.
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...