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.
Related
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 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
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
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.
So my dad is using the old S4 as 2nd phone for multimedia, gps etc. Recently he went and installed and app from store. He locked the phone and when he tried to unlock it, the phone started giving pink screen after swiping to unlock. I tried reinstalling the lineage os but after a reboot the same thing happend. Tried another rom but the phone got stuck in bootloop(keeps rebooting when trying to start up). So I decided to revert to stock ROM, flashed the pit though odin because it was throwing errors about it missing, then went and flashed the stock rom. Tried to start aaaaaand - bootloop. Any suggestions on what to do?
Try flashing the latest stock ROM again without a pit file and with the original Samsung USB cable.
audit13 said:
Try flashing the latest stock ROM again without a pit file and with the original Samsung USB cable.
Click to expand...
Click to collapse
Ok, I tried flashing stock lollipop(though not the one for my country). It tries to boot up, goes through the first model screen, starts the "samsung" animation, but only gets to show 3 letters before it goes black and restarts after 10-15secs. Is it hardware damaged or what? It is was used as secondary phone because it wouldnt read sim card anymore.
DId you perform a factory reset using stock recovery?
audit13 said:
DId you perform a factory reset using stock recovery?
Click to expand...
Click to collapse
yup
It could be pure coincidence but is it possible the internal memory is damaged? Possible loose connection?
audit13 said:
It could be pure coincidence but is it possible the internal memory is damaged? Possible loose connection?
Click to expand...
Click to collapse
dunno, the phone was used lately by my dad and he usually takes good care of phones. Before it was my sis phone(until sim wont read anymore) and well, it got dropped a lot.