hardware problem? - Samsung Galaxy S9+ Questions & Answers

My s9+ "died" over Christmas and wouldn't start. The internal storage only displayed about 5mb in recovery and the PC wouldn't recognise it.
I then got an s10+, which whilst good, isn't something I really wanted or felt was a worth while upgrade.
I since then managed to get my s9+ up and running again by flashing the latest stock firmware and using the PIT to partition and get the right storage space back.
I gave the s9 to my son, however every week or 2, the device goes in to an infinite boot loop as it did at Christmas and the only way to fix is to factory reset.
Having flashed a fresh firmware with PIT, I'm confident another flash won't fix it, but do wonder if anyone has any ideas or has seen this behaviour before? Am I facing a hardware fault, or is there some magic I can perform to fix it?
I have wondered if underclocking the CPU may fix it, but in not even be a CPU fault...
My frustration is, that it does work instantly after a factory reset for at least a week or two, so I'm not sure why it keeps failing in the same way after that time. My son has no software the same as mine installed, so I don't think it's any of the applications.

You fix hardware problem with software workarounds. Try samsung service center instead.

sarjarim said:
You fix hardware problem with software workarounds. Try samsung service center instead.
Click to expand...
Click to collapse
Urm... not quite sure what you mean. I'm not confident it's a hardware issue ad the device works for a period of time before is goes in to the endless boot loop.

I suspect it's a hardware problem, please visit your nearby service center.

riso123 said:
Urm... not quite sure what you mean. I'm not confident it's a hardware issue ad the device works for a period of time before is goes in to the endless boot loop.
Click to expand...
Click to collapse
i also suspect that its a hardware problem. sorry man, off to the service center it goes

Youdoofus said:
i also suspect that its a hardware problem. sorry man, off to the service center it goes
Click to expand...
Click to collapse
It does feel like a hardware issue. I just don't understand why it will work for a period of time before suddenly failing again.

Related

[Q] "Insert sim card" error :(

Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Habitats said:
Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Click to expand...
Click to collapse
You can refuse to believe in gravity too, but falling from high distances will still hurt.
If you tried more than one SIM in the phone and none work, but those same SIMs work in other phones, than more than likely, it is hardware related.
Did you check you imei?
078gregory brings up a good point. So if it's not missing IMEI info, THEN it's likely hardware.
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Habitats said:
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Click to expand...
Click to collapse
Don,t forget to press THANKS button on ctomgee
Hi people. I have the same problem Habitats decribes. Mi s2 is stuck in flightmode and cant get out! i have reset the phone in every kind of way but no succes. Now i read here on this forum that flashing my phone to ICS 4.0.3 can help solve the problem. I'm on 2.3.6 now. This flightmode thing happened al over sudden. I have done nothing strange with the phone. Its not rooted either. I was planning to go to a samsung servicepoint and let them check whats wrong. But now i read this thread and see that i can relate to this problem of Habitats. I think a also will try to flash ICS 4.0.3 and watch what happens. But theres another problem. KIES don't recognize my phone anymore so what can i do? Can someone please help me out? Thanks in advance
I'm having the exact same problem, could you please tell me which rom worked for you Habitats? Thanks in advance!
Update:Last tuesday i went to the vodafone store were they have a samsung service department also. I explained my problem to them but they don't seem to recognize the problem. Although i read that many people here at xda's and over the internet have similar issues with this phone.Strange! So they sent it to the repair centre. Yesterday i could see in the track and trace menu of the repair centre that my fone was ready and send back to the vodafone store. Status: Boardswap. So they swapped the whole board! Didn't know that the problem was that serious! So i hope i can pickup my galaxy s2 soon this coming week!! I can't wait!I'm on my old HTC Touch HD now. Its ok with the windows but on Android....Arggghh!! Whatsapp is a pain and more. Its so laggy!. I will give an update soon again!

[Q] Back from repair - does it sound fixed to you?

Hi all,
Got, or rather gonna get, it back on Wed. This is a 2nd warranty repair trip this fall for the same problem: phone reboots at random sometimes 10+ times a day, sometimes not all. And random as scrolling through Settings random. Samsung system reports it as:
*****
Original Problem:
TECHNICAL INQUIRY - POWER - POWER CYCLE
Problem found:
WON'T DOWNLOAD SW/PRL
Solution:
S/W UPDATED
*****
It felt like a hardware problem to me. Looks like all they did is updated some software and/or PRL. Does that sound like it could possibly resolve the random reboots problem I've been having? I'm skeptical and thought I'd ask.
Thanks!
SM05 said:
Hi all,
Got, or rather gonna get, it back on Wed. This is a 2nd warranty repair trip this fall for the same problem: phone reboots at random sometimes 10+ times a day, sometimes not all. And random as scrolling through Settings random. Samsung system reports it as:
*****
Original Problem:
TECHNICAL INQUIRY - POWER - POWER CYCLE
Problem found:
WON'T DOWNLOAD SW/PRL
Solution:
S/W UPDATED
*****
It felt like a hardware problem to me. Looks like all they did is updated some software and/or PRL. Does that sound like it could possibly resolve the random reboots problem I've been having? I'm skeptical and thought I'd ask.
Thanks!
Click to expand...
Click to collapse
Depends on what all you've tried before sending it in. Have you tried wiping the phone and flashing multiple roms to see if the issue persisted? If so, then it's most likely a hardware issue. If not, then it's possibly a software issue.
dsmboost said:
Depends on what all you've tried before sending it in. Have you tried wiping the phone and flashing multiple roms to see if the issue persisted? If so, then it's most likely a hardware issue. If not, then it's possibly a software issue.
Click to expand...
Click to collapse
I've flashed it back to stock 2 times before sending it in. In both cases phone would continue exhibiting the same behavior ie sporadic reboots for about a day, especially in the first few hours after re-flash. It'd then settle in into a no-reboots state. Not sure what to contribute that too. I did do a full wipe and didn't load practically any apps on it. So, may be certain parts of the RAM weren't being exercised. I don't know, just guessing here. Not sure what to make out of that pattern I mentioned though.
Thanks for your help.

[Q] Phone keeps shutting down

Hi guys.
My phone shuts down at random moments. I can boot it up again by holding the power button for about 10 seconds. Sometimes, not always, the phone feels hot and batterylife dropped. I have been struggling with this problem ever since i got this phone. I hoped to solve it with installing a new kernel and rom. I am now on Slimbean 3.1.0. The phone was initially on XLQ6 4.0.4. This didn't change anything, unfortunately.
I have also tried:
- removing external SD
- placing a new battery (which has no room to move, in case anyone suggests the battery might be moving)
- wiping caches
The strange thing is that my friend has bought his i9100 together with mine in the same order. He is also on XLQ6 and is experiencing the same issues. Less often than me, however.
My smalband is still on XLQ6. Is it possible that this causes my problems? Or is it more likely that my friend and me simply bought phones from a bad batch or something (hardware related)? I really don't want to send back my phone. That is my absolute last resort.
EDIT: Problem solved! Installing the application "Load Monitor" and enabling the "wake lock" function has done the trick. No more shutdowns or reboots!
Anyone?
2 devices with the same issue?
I'd be at the store where I bought it right now.
I will do that when I am absolutely sure that it is hardware related. However, if anyone has a potential solution I would really like to solve this issue myself.
Achtendertig said:
I will do that when I am absolutely sure that it is hardware related. However, if anyone has a potential solution I would really like to solve this issue myself.
Click to expand...
Click to collapse
Same with me. change from 4.0.4 WLPT to 4.0.4 WLPY but problem still presists.
Does anyone know if changing smalband (if that is possible?) could make a difference? Because that is the only similarity to the original state of my phone. A lot of AT&T users in the USA experienced the same problems also with 4.0.4. However, nobody can come up with a solution.
Achtendertig said:
Does anyone know if changing smalband (if that is possible?) could make a difference? Because that is the only similarity to the original state of my phone. A lot of AT&T users in the USA experienced the same problems also with 4.0.4. However, nobody can come up with a solution.
Click to expand...
Click to collapse
If it is heating near the camera, it's facing death soon.
If it is new and warranty isn't voided, why not flashing the carrier ROM and get a new one?
gastonw said:
If it is heating near the camera, it's facing death soon.
If it is new and warranty isn't voided, why not flashing the carrier ROM and get a new one?
Click to expand...
Click to collapse
Because I don't like to lose my phone for a couple of weeks. And I prefer to fix these things myself. I have seen so many topics about this on XDA and Google. There must be a solution to it.
Is it possible that these problems are caused by my modem? That is the only unchanged thing since I have had this phone.
I might have found a possible solution. I've read something on a Dutch forum about sim-cards causing these issues. So I have placed a new sim-card and the problem hasn't appeared in the last 3 days. Before that, the problem was occuring about 3-6 times in one day. It's too early to say this has solved my problem, but it definitely made a difference so far. If it keeps functioning perfectly for the next couple of days I will close this topic.
Symptoms were merely reduced. Phone still shuts down approximately each 2 days. Much better than it was before though. Why would a sim-card change reduce, but not solve the problem? This is starting to hurt my brain.
Achtendertig said:
Symptoms were merely reduced. Phone still shuts down approximately each 2 days. Much better than it was before though. Why would a sim-card change reduce, but not solve the problem? This is starting to hurt my brain.
Click to expand...
Click to collapse
You may experience sleep of death. What WiFi chipset do you have? I had the same issue on a Murata Wi-Fi chipset.
Yup, Murata chipset. I've googled some more on SoD. I have now installed an app called "Load Monitor" and enabled Wake Lock in preferences. This should prevent the phone from going into deep sleep, apparantly.
Some portugal carrier had a problem with lte sim card or something like that.
I really don't see how a sim card can actually mess with a phone.
Maybe the enabling of some features screws it up.
Sent from the little guy
Achtendertig said:
Yup, Murata chipset. I've googled some more on SoD. I have now installed an app called "Load Monitor" and enabled Wake Lock in preferences. This should prevent the phone from going into deep sleep, apparantly.
Click to expand...
Click to collapse
In my case Samsung Service Team replaced the motherboard. My new MB has a Samsung Electronics wifi chipset. Two weeks now and no SoD.
That sounds good. However, ever since I have installed Load Monitor my phone runs fine. It drains approximately 40% of my entire battery, but it lasts easily until the end of the day.
But again, I shouldn't get too excited. Sim-card change seemed to work in the first few days as well.
Will be continued...
It has been over a week since I have installed Load Monitor. My phone hasn't shut down once. Problem appears to be solved! I hope more people will read this topic, because I have seen a lot of desperate people during my search to a solution.
The only disadvantage is the battery usage of the application. I now have approximately 40-50% at the end of the day instead of 60-70%.
Achtendertig said:
It has been over a week since I have installed Load Monitor. My phone hasn't shut down once. Problem appears to be solved! I hope more people will read this topic, because I have seen a lot of desperate people during my search to a solution.
The only disadvantage is the battery usage of the application. I now have approximately 40-50% at the end of the day instead of 60-70%.
Click to expand...
Click to collapse
Unistall it.
Sent from the little guy
gastonw said:
Unistall it.
Sent from the little guy
Click to expand...
Click to collapse
Because?
Mo' juice yo.
Sent from the little guy

Hardware or Software-level Problem? [Battery Issue]

This is bugging me for such a long time now. I've had this problem for such a long time. The issue is that everytime the phone reaches 100% of charge, and leaving it for a while (maybe like 5 mins-ish?), The phone suddenly reboots (hard reboot not soft-reboot) and continues to charge but in the idling turned-off mode (only the battery logo is displaying).
Solutions I've tried but didn't or barely work:
Replacing the Battery itself
Switch to different Kernels
Switch to different ROMS (MIUI, AOSP, OOS etc.)
Full drain to 0% and charge to 100% while off
This leaving me confused af and irritated because everytime I want to charge my phone overnight or I just want to leave my phone charged all the time to minimize the battery degradation, the phone reboots completely out of the blue, letting me miss the notifications that I haven't read yet. I need help on this please.
Flash your device via miflash
hidden.hero said:
Flash your device via miflash
Click to expand...
Click to collapse
I'll try that one once again, after I backup my files on my phone, and update once I've done it, and see if it helped or not, thanks for suggesting
You are welcome
hidden.hero said:
Flash your device via miflash
Click to expand...
Click to collapse
Unfortunately it doesn't solve the problem. The issue still persists
you need to take the device to the service I guess this is not a software problem
Probably an issue with the board already, either due to a fall or maybe the device you bought may have just have been defective. I would have suggested that you brought it to a service center (since you said you had the issue for a longtime then maybe you could have had it serviced while it still had warranty)
mecoromeo said:
Probably an issue with the board already, either due to a fall or maybe the device you bought may have just have been defective. I would have suggested that you brought it to a service center (since you said you had the issue for a longtime then maybe you could have had it serviced while it still had warranty)
Click to expand...
Click to collapse
Oh I forgot to mention, yes it may have been a long time issue, but it just started to happen right around 3 months after I bought it. I bought my phone brand new last year, and it didn't have the issue I'm facing now. Sadly, the warranty doesn't cover the battery issue, since I just bought it form a random retail store (not Xiaomi)
Ordinary_Smartphone_User said:
Oh I forgot to mention, yes it may have been a long time issue, but it just started to happen right around 3 months after I bought it. I bought my phone brand new last year, and it didn't have the issue I'm facing now. Sadly, the warranty doesn't cover the battery issue, since I just bought it form a random retail store (not Xiaomi)
Click to expand...
Click to collapse
Sorry to hear that. Well, it would be best to have it checked by a repairman by this point since based on all the info you've provided you've tried all the troubleshooting steps software wise, so it may be the board by this point. Or if that random store offered you a repair warranty (most rando stalls in my country has that, not sure about yours) then you may swing by there
what about charger?
seems like the only thing that you didnt check
mecoromeo said:
Sorry to hear that. Well, it would be best to have it checked by a repairman by this point since based on all the info you've provided you've tried all the troubleshooting steps software wise, so it may be the board by this point. Or if that random store offered you a repair warranty (most rando stalls in my country has that, not sure about yours) then you may swing by there
Click to expand...
Click to collapse
Well if it's a hardware issue from the board itself, maybe I'll just pass for now. The repair warranty though doesn't really cover some major problems like motherboard and battery, it actually needs to paid so ig it's a no for me. I'll just replace it myself over time if the board breaks itself.
jordan_yoong_1 said:
what about charger?
seems like the only thing that you didnt check
Click to expand...
Click to collapse
I had no issues on charger either. I used a different Xiaomi charger from another phone, and the battery issue is still there. I even opted in using a samsung charger with usb-c, and still the problem persists.

S21 crashing/rebooting 1-2 times/day. Any tips on troubleshooting?

I have as SM-G991U (256 GB S21 US version, stock everything but using Nova Launcher) that is randomly freezing/crashing then rebooting on me 1-2 times/day. Does android have any kind of crash log I could look at to try and figure out what's causing the problem? On the samsung forums, their support reps suggest running in Safe Mode, which I have, but it's not very useful because I can't reproduce the problem on demand and it usually happens 1-2/day, but sometimes less, so unless I just ran in safe mode all the time, that wouldn't tell me much. Plus, it would only tell me it's an issue caused by one of a hundred or so apps which, again, is not helpful.
So I'm hoping there is a crash log or something somewhere because I have no idea what triggers the crashes. The other night, it was sitting on a wireless charger, the screen wasn't on, then all the sudden it rebooted. It's not specific to any app or anything I'm doing. If there are no crash logs (which would be frustrating and disappointing), any other troubleshooting ideas are welcome!
Look for a memory leak. Typically a poorly written 3rd party apk.
Try clearing system cache.
Make sure auto restart isn't enabled...
dougleto said:
I have as SM-G991U (256 GB S21 US version, stock everything but using Nova Launcher) that is randomly freezing/crashing then rebooting on me 1-2 times/day. Does android have any kind of crash log I could look at to try and figure out what's causing the problem? On the samsung forums, their support reps suggest running in Safe Mode, which I have, but it's not very useful because I can't reproduce the problem on demand and it usually happens 1-2/day, but sometimes less, so unless I just ran in safe mode all the time, that wouldn't tell me much. Plus, it would only tell me it's an issue caused by one of a hundred or so apps which, again, is not helpful.
So I'm hoping there is a crash log or something somewhere because I have no idea what triggers the crashes. The other night, it was sitting on a wireless charger, the screen wasn't on, then all the sudden it rebooted. It's not specific to any app or anything I'm doing. If there are no crash logs (which would be frustrating and disappointing), any other troubleshooting ideas are welcome!
Click to expand...
Click to collapse
Hi mate
For logs info check here and here
You can always flash firmware , using home_csc , to avoid factory reset the phone , if the problem is system related it will help
If is app related
Try booting in safe mode to see if problem goes away...
MAX 404 said:
Hi mate
For logs info check here and here
You can always flash firmware , using home_csc , to avoid factory reset the phone , if the problem is system related it will help
If is app related
Try booting in safe mode to see if problem goes away...
Click to expand...
Click to collapse
Thanks! I'll definitely try these out. I tried safe mode, the trouble is it's not really great as a diagnostic because the phone will go from 4-24 hrs between resets during normal operation, and since a phone in safe mode isn't terribly useful, it's hard to keep it in safe mode for long enough to see if that fixed the issue, if that makes sense. And then, if it did fix the issue, it just narrows it down to 1 out of a hundred apps! But maybe I'm missing something. Is there additional information I can find if I run in safe mode that would help suss out the problem?
blackhawk said:
Look for a memory leak. Typically a poorly written 3rd party apk.
Try clearing system cache.
Make sure auto restart isn't enabled...
Click to expand...
Click to collapse
Thanks! I know how to clear cache but not how to check for memory leaks. Do you have a tool you'd recommend to do that? And I had never heard of auto restart before, so thanks for that. I confirmed that it is NOT enabled (that would have been a face palm moment!).
dougleto said:
Thanks! I'll definitely try these out. I tried safe mode, the trouble is it's not really great as a diagnostic because the phone will go from 4-24 hrs between resets during normal operation, and since a phone in safe mode isn't terribly useful, it's hard to keep it in safe mode for long enough to see if that fixed the issue, if that makes sense. And then, if it did fix the issue, it just narrows it down to 1 out of a hundred apps! But maybe I'm missing something. Is there additional information I can find if I run in safe mode that would help suss out the problem?
Click to expand...
Click to collapse
Is not easy , you just need to be methodic
See if you can find anything useful in the logs first
Reflash firmware , use home-csc , see if it help
Have you notice if the phone fails under any specific circumstances?
If that does not help and if you can really relate the problem with any specific app you may try to freeze or uninstall suspicious app and let it run for a day , Package disabler app is a good option , it is easy to enable or disable app but is not free, you could try this one , is a debloater tool , it allow you to disable app... may be easy that having to uninstall / install by hand
I'm also having the same problem. Had the phone since June, it didn't start to occur until late August, which leads me to suspect it is an update related issue.
GillBates21 said:
I'm also having the same problem. Had the phone since June, it didn't start to occur until late August, which leads me to suspect it is an update related issue.
Click to expand...
Click to collapse
I'm glad you posted today, I've been meaning to post again here because I tried troubleshooting and am still having issues. In fact, it crashed twice today when I was trying to send a text message.
I installed one of the log applications (can't remember which one at the moment) but it wasn't really helpful. They didn't seem to catch any information related to a crash even though they were logging data at least twice when it crashed.
Then I tried reflashing using home-csc using ODIN and that ended up soft-bricking my phone (and yes, I followed all the instructions and used home-csc) so I had to reflash everything and do a full factory reset. That seemed to help, reducing the crashes from once/day to once/2-3 days for a few weeks, but now it's back to ~once a day (sometimes more, sometimes less).
So if anyone has any other idea, I'm all ears. When I was reflashing and stuff, I noticed in the recovery mode (or whatever it's called) options that you can look at logs. Does anyone know if one of those logs would have crash-related data or any other ideas of what to try? This is incredibly frustrating, especially that it's persisting after a factory reset. Argh!
dougleto said:
I'm glad you posted today, I've been meaning to post again here because I tried troubleshooting and am still having issues. In fact, it crashed twice today when I was trying to send a text message.
I installed one of the log applications (can't remember which one at the moment) but it wasn't really helpful. They didn't seem to catch any information related to a crash even though they were logging data at least twice when it crashed.
Then I tried reflashing using home-csc using ODIN and that ended up soft-bricking my phone (and yes, I followed all the instructions and used home-csc) so I had to reflash everything and do a full factory reset. That seemed to help, reducing the crashes from once/day to once/2-3 days for a few weeks, but now it's back to ~once a day (sometimes more, sometimes less).
So if anyone has any other idea, I'm all ears. When I was reflashing and stuff, I noticed in the recovery mode (or whatever it's called) options that you can look at logs. Does anyone know if one of those logs would have crash-related data or any other ideas of what to try? This is incredibly frustrating, especially that it's persisting after a factory reset. Argh!
Click to expand...
Click to collapse
So what I tried to do is roll back all the default google app updates. Ex: Android system webview, Google app itself, etc etc. I factory reset it without backing up any apps (but pictures and messages etc), It was working for a few days and then it happened again. Which further reinforces my thinking that my problem is software based.
GillBates21 said:
So what I tried to do is roll back all the default google app updates. Ex: Android system webview, Google app itself, etc etc. I factory reset it without backing up any apps (but pictures and messages etc), It was working for a few days and then it happened again. Which further reinforces my thinking that my problem is software based.
Click to expand...
Click to collapse
So I'm curious why you think that means it's a software issue. If this isn't a widespread issue with the S21 and after we've both done a factory reset and still have the issue, that makes me think it could be a hardware issue. Of course, there could be some software incompatibility with an app that most people don't have installed or a bluetooth connection or something, which is why I really want to find a useful crash log (and find it rather absurb how hard it is to find a useful crash log on android, come on guys, it's a mature OS, some kind of crash log seems pretty basic!), because otherwise, it could be a ton of issues and I can't reproduce it. Ugh.
The reason is that the "few days" after the reset and restoring pictures, messages (but not apps) from backup, where there were no crashes at all (where previously it would happen at least 2 times per day).
GillBates21 said:
The reason is that the "few days" after the reset and restoring pictures, messages (but not apps) from backup, where there were no crashes at all (where previously it would happen at least 2 times per day).
Click to expand...
Click to collapse
Got it, that makes sense. I'm on t-mobile and just got an update this morning. We'll see if that improves anything because my device restarted 4 times yesterday
I havent had a crash like this since i disabled chrome and other google stuff, and downgrading google apps lol.
GillBates21 said:
I havent had a crash like this since i disabled chrome and other google stuff, and downgrading google apps lol.
Click to expand...
Click to collapse
How did you disable chrome and what other google stuff did you disable? (There's obviously quite a lot of google services that can't be disabled)
After the most recent monthly update, my phone has gone from rebooting multiple times/day to once every 2-3 days, which is more manageable but still super annoying. It is incredibly frustrating to me that there are no good tools to troubleshoot a crash (at least that I've ben able to find). Honestly, it's driven me to consider an iPhone for the first time in my life .
My trouble is back... I will be scheduling a fix with samsung soon so I can RMA it
Check the below link. This seems to be a hardware problem which got solved after Samsung replaced the motherboard.
Samsung Restart problem
So I bought this phone for my wife. Since I received the phone, after a day the phone started crashing whatever app she was on and then take you back to lock screen without having to go through a full restart process but it was definitely a restart as you would need to enter your pin again as opposed to fingerprints.
Since it was within 15 days of purchase I returned and reordered another one from Samsung, and to my surprise exact same issue. What are the odds of having two brand new phones having exact same issues.
This leads me to believe it must be a software issue. I just received this 2nd new phone last Friday.
Yeah, I think what I was experiencing was a hardware issue (it definitely went through the full restart process, not what is described in the previous post). And from the link posted by sandystays above, it looks pretty common. I contacted Samsung support and was not impressed at all. They walked me through a number of troubleshooting steps that weren't helpful then had me take my phone to UBreakIFix. I did, they ran a diagnostic and their tools couldn't find anything wrong so they said Samsung should replace it.
Contacted Samsung, told them I had taken it in. They said I needed to take it to a technician (again, right after telling them I just had). They then said, oh, you'll have to mail it to us and you'll get your phone back in 7-10 business days. Their suggestion for what to do for a phone in the meantime? Buy a prepaid phone then return it when I get my phone back (which a) is unethical and b) wouldn't work anyways since they're locked). Ridiculous. They also admitted that this is a very common problem, so I asked why they just won't send me a replacement device if it's so common to which they had no real answer, just "that's our policy".
Eventually, I contacted T-mobile (my carrier) and was very pleasantly surprised. After me telling them the issue and the steps I'd taken to troubleshoot it, they sent me a replacement phone (recertified, but still) that arrived in 2 days. WAAAYYYY better than Samsung. The entire process made me a bit jealous of my wife's iPhone. If she had had a similar issue, we could have taken it to an apple store and not had the whole "our policy is that you have no phone for 7-10 business days" nonsense from Samsung AND the backup and restore process is still way better on iPhones than on any android I've ever owned. How there is no easy and reliable backup/restore mechanism on android after so long is beyond me.
Bottome line: if you have a similar issue, it's very likely a hardware problem (my replacement phone has been fine for 3 days now). And avoid Samsung support if you can!
dougleto said:
Yeah, I think what I was experiencing was a hardware issue (it definitely went through the full restart process, not what is described in the previous post). And from the link posted by sandystays above, it looks pretty common. I contacted Samsung support and was not impressed at all. They walked me through a number of troubleshooting steps that weren't helpful then had me take my phone to UBreakIFix. I did, they ran a diagnostic and their tools couldn't find anything wrong so they said Samsung should replace it.
Contacted Samsung, told them I had taken it in. They said I needed to take it to a technician (again, right after telling them I just had). They then said, oh, you'll have to mail it to us and you'll get your phone back in 7-10 business days. Their suggestion for what to do for a phone in the meantime? Buy a prepaid phone then return it when I get my phone back (which a) is unethical and b) wouldn't work anyways since they're locked). Ridiculous. They also admitted that this is a very common problem, so I asked why they just won't send me a replacement device if it's so common to which they had no real answer, just "that's our policy".
Eventually, I contacted T-mobile (my carrier) and was very pleasantly surprised. After me telling them the issue and the steps I'd taken to troubleshoot it, they sent me a replacement phone (recertified, but still) that arrived in 2 days. WAAAYYYY better than Samsung. The entire process made me a bit jealous of my wife's iPhone. If she had had a similar issue, we could have taken it to an apple store and not had the whole "our policy is that you have no phone for 7-10 business days" nonsense from Samsung AND the backup and restore process is still way better on iPhones than on any android I've ever owned. How there is no easy and reliable backup/restore mechanism on android after so long is beyond me.
Bottome line: if you have a similar issue, it's very likely a hardware problem (my replacement phone has been fine for 3 days now). And avoid Samsung support if you can!
Click to expand...
Click to collapse
On the second phone I still have the 2wk window to return. I am contemplating if I should just return altogether. I had bought an s21 Ultra as well and that seem to be working OK.
Two s21+ phones with same issue, what are the odds of hardware problem? But what if it is the entire batch that is bad.
isiddiqi said:
On the second phone I still have the 2wk window to return. I am contemplating if I should just return altogether. I had bought an s21 Ultra as well and that seem to be working OK.
Two s21+ phones with same issue, what are the odds of hardware problem? But what if it is the entire batch that is bad.
Click to expand...
Click to collapse
Your issue sounds different to me. Mine definitely fully rebooted, I have no idea what is going on with yours, it sounds like your crashes are locking the phone or something, that could definitely be software. Good luck!

Categories

Resources