I have a Galaxy S4 (i9505) that had a cracked screen which rendered the phone unusable (it looked like a squid had squirted ink all over the screen from within, touch still worked, but I could barely see a thing), so I bought a replacement lcd/digitiser, etc, took the phone apart, replaced the screen, put everything back together and now...I cannot get past the boot screen.
I was previously running CM12 (some nightly build from a couple of months back) and had had no troubles with it at all.
I have ClockworkMod Recovery 6.0.4.7 running as recovery and can flash, wipe, etc, but none of this works.
I've currently only tried wipe data/factory reset and re-flashing CM12 and CM11.
I'm considering flashing TouchWiz, full stock, to see if that works, but really...I hate TW so it's far from ideal.
Then again, having a broken phone is less ideal than TW, so I'll take anything at this point
Does anyone have any suggestions?
Have I messed something in the hardware that could cause this?
The fact that I can get to recovery and/or bootloader, says to me that things should be ok, but I'm quite confused.
Should I try flashing a stock ROM with ODIN instead?
Am I missing something simple?
Any help is most appreciated.
Patrick.
have you ever check the connection again, like ribbon cable etc. ? screen replacements won't affect on NAND flash (if you doing it right and not damaging any other components)
Check the charging flex cable connector.
Sent from my SM-G900F using XDA Free mobile app
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
I had an S4 in for LCD replacement, everything went fine. Possibly the EASIEST phone repair possible.
The phone was reassembled and worked fine, put it up for sale and updated etc. After a few days of it sitting there I went to turn it back on and it wouldn't boot, just hung at the Samsung logo and wouldn't boot recovery.
I left it and thought i'd sort it the next day and went to proceed to flash with Odin until the battery charge logo came on so I knew it was working and then I turned it on and it all worked fine.
It was working fine so I thought it was a one off so turned it off and it happened again. Now im constantly flashing via Odin to try and get anything out of it, sometimes it will boot up get past the Samsung logo then it will freeze.
I have read near enough every threat on the subject, I doubt I'll get an answer here but I'll keep this bumped everyday in hope there's somebody who knows what's going on.
Here's what I've tried
- Flashed latest rom via odin
- Flashed 4.4.2 via odin (supposed to fix this issue)
- Flashed PIT & latest rom via odin
- Flashed PIT & 4.4.2 via odin
I don't know what else to do
Check hardware.
GDReaper said:
Check hardware.
Click to expand...
Click to collapse
What hardware...?
I have looked at the logic board and can't find anything wrong with it.
Well, it can't be the software because you already tried a bunch. The only constant thing is the hardware. May be a semi-functional power button. I don't know.
GDReaper said:
Well, it can't be the software because you already tried a bunch. The only constant thing is the hardware. May be a semi-functional power button. I don't know.
Click to expand...
Click to collapse
All buttons work fine.
Doesn't look like eMMC is the issue because it's writing to the NAND, there's probably an IC with a bad solder joint which explains why it randomly boots sometimes, the only problem is I don't know which IC it is.
Reflowed U800 IC 140c and i9505 booted up no problems
I restarted my S4 this evening and now it won't boot past the SAMSUNG logo. I have tried a variety of things to get it going but none have worked.
1) Soft boot
2) Pulled battery and let it sit awhile
3) Tried to boot into Safe Mode (stuck on the same spot with no indication of going into safe mode)
4) Wipe cache from CWM recovery mode
5) Reboot from CWM recovery mode
Everything is pretty well backed up but after looking at my sdcard it appears that my camera reverted to internal memory about a month ago so I am after any ideas to get those images.
My phone is rooted and running an old 4.2.2 stock Android OS with USB debugging enabled. I was wondering if by re-flashing the OS it might fix the boot issue and be able to recover the images. Or maybe even flash CM. Or maybe some other thing. I found something about adb but I don't want to do anything else yet until someone more savvy than me weighs in.
Unless it's a hardware issue, then flashing a ROM might work.
The other option is to try a reflow. Reflow means heating your phone up so that the solder becomes liquid and any cracks in the solder (which can cause a bad contact), or any piece that isn't seated right, will be remedied.
did u tried to flash stock firmware using odin?
Deleted
I got it going. I first spent a number of hours getting to know adb which was a dead end because I couldn't get it to see beyond the base directory. I then just flashed the stock rom and everything was there including things that shouldn't be like apps, contacts and texts. The phone is back exactly where it was before it boot locked without having to mess with a single thing. I am grateful but a bit confused.
So. Basically. Today my S7 edge started crashing after the Samsung Logo.
What I did was flash the stock firmware to restore the stock ROM after coming from a custom one. I'm sure I did everything correctly, flashed the 4 parts of the firmware via Odin correctly and it even showed me a "PASS!".
After it succeeded and rebooted though it crashed while performing a factory reset. Then I tried to boot it into the recovery by myself and it kept crashing while saying "Erasing."
I'm out of ideas. Should I reflash? Or might it be a broken motherboard?
Oh well.
reflash stock with odin or samsung software. I doubt its a haydware problem. jusr stj went wrong while flashing
yaro666 said:
reflash stock with odin or samsung software. I doubt its a haydware problem. jusr stj went wrong while flashing
Click to expand...
Click to collapse
I did that with several stock ROMs already. Nougat and MM.
When it says erasing how long did you wait? You have to wait like a minute or two to get the recovery menu to show sometimes right after flash. You flashed with CSC right and not home_csc?
If you want you can try flashing custom recovery and manually formatting the /system and /data partition then flash again and try booting it again.
benjamen50 said:
When it says erasing how long did you wait? You have to wait like a minute or two to get the recovery menu to show sometimes right after flash. You flashed with CSC right and not home_csc?
If you want you can try flashing custom recovery and manually formatting the /system and /data partition then flash again and try booting it again.
Click to expand...
Click to collapse
Thanks for the reply.
I always give it time. But it crashes even at the "Erasing" screen. Like... It boots up. Gets into that screen and crashes after 2 seconds. It doesn't even reboot.
Yes. I always flashed CSC. Not the home one.
I'm not sure if a custom recovery like TWRP would help because if the stock one doesn't work, why would TWRP work?
Had this exact issue before on a S8, could not fix it.
Sometimes it could be just the battery needing to be replaced or every connection to the logic board needed reseating. PITA to diagnose as you have to take the rear glass cover off, done by using plastic flexible thin cards and a razor blade to initially lift up the glass edge a bit to slide the plastic thin card to separate the adhesive.
benjamen50 said:
Had this exact issue before on a S8, could not fix it.
Sometimes it could be just the battery needing to be replaced or every connection to the logic board needed reseating. PITA to diagnose as you have to take the rear glass cover off, done by using plastic flexible thin cards and a razor blade to initially lift up the glass edge a bit to slide the plastic thin card to separate the adhesive.
Click to expand...
Click to collapse
So, basically, the phone's fcked?
Yeah. Your phone is showing Samsung logo white text splash screen, then goes off and reboots 10 seconds after right? That's what mine did.
benjamen50 said:
Yeah. Your phone is showing Samsung logo white text splash screen, then goes off and reboots 10 seconds after right? That's what mine did.
Click to expand...
Click to collapse
Mine doesn't always reboot. It just turns off. The reboot mostly happens only then after I tried to access the recovery.
Hi, I've had a S4 LTE for over a year, tried quite a few different roms on it and eventually settled for Diamond John's RR 5.8.5 version. This was working more or less okay until a few weeks ago when the phone crashed during some activity with that blue screen thing.
After that I could not start the rom properly again, it always either boot loops or displays the blue screen. I then tried reinstalling the rom, other roms, bootloader and eventually the stock rom but it still behaves the same - crashes, bootlops and/or blue screen.
I think I did follow the recommended procedures, ie wiping everything, starting from scratch and using appropriate files but can't be 100% sure since I'm not an Android wiz. Hence my question: do you think there is something else I can try to recover this phone or does this look like hardware failure?
Thanks in advance