4G But No Texts/Calls FIX - Sprint HTC One (M9)

Sunday evening, I went through HELL fixing my phone. Once I realized a text wouldn't go through, I tried the data and calling. Only data worked. I've rooted my phones since the Evo 4G and never had this issue before. I called Sprint at 3:30pm, spent an hr which got me nowhere and actually made it worse. She told me to do the ##72786# which shows the MDN and MSID. I've done this in the past for activation sake on previous phones, on the M9 it doesn't allow you to manually change the values which was a major problem. Once i did the reset, both values were the same and incorrect. At this point I was like OH SHIIT, cause I just realized you can't manually input the values. And because those values have to be your number, I knew was screwed...after the restart I lost my LTE as well since Sprint didn't know this was my phone due to no MDN/MSID values. I thought for sure I would have to do a new fresh install which I did NOT want to do as everything with the phone was perfect and a fresh install takes a looot of time to backup everything, reinstall, make sure settings and everything are like before. I told her to activate my S7 and reactivate the M9 to see if that did the trick to force the M9 into hands free activation and push through the MDN/MSID. I wasn't hopeful at all since I activated the M9 BEFORE I rooted it just to be sure and also cause I bought it off ebay so had to make sure all way well.
Once i got off the phone, I started searching on google/xda for a solution. It's quite a specific issue and similar ones were sparse and had a range of reasons for the issue. Mind you, all was well before this, it's basically the stock Venom rom, no major tweaking and this issue just randomly appeared for no apparent reason. I never used Titanium Backup up to this point(1 yr using the phone) or any Rom backups so I was like, might as well since I'm gonna have to start flashing to see if it fixes it. First I flashed the venom rom to see if a fresh flash did the trick...possibly the clean install requests MDN/MSID from Sprint to get the phone working. Didn't fix it. Next, I flashed the stock rooted rom which thankfully I saved when I first rooted the phone. Phone booted up, BINGO! Instant 4g connection. Phew, thank God. Then, I flashed venom again but with a full wipe to see if the stock install carried the MDN/MSID over, didn't fix it. I was so pisssed cause at this point I knew I was screwed.
Mind you, backing up/flashing and at the same time searching and trouble shooting is VERY time consuming! A fresh flash/boot alone takes maybe 10 min. I was also doing some extensive searching for the best SMS/MMS backup out there as I always keep my text records(which I'm making another thread to discuss). It's almost midnight and im PISSSED. My entire Sunday evening wasted and a random stupid problem on my phone that came out of the blue for NO reason. I'm guessing Sprint did some network update and the phone need a Profile/PRL update which it couldnt get. Not sure how that works.
I can't find the thread it was mentioned in, and I searched MANY, but someone mentioned the Sprint PRL patch(for a different issue) in Venom Hub. I didn't think that would do anything as that's preferred roaming list. I had nothing to lose and it was a Sprint specific patch so I tried it. I never used Venom Hub as I mentioned the phone is pretty much stock venom so I didn't know it was there. Prior to this I checked Venom tweaks, nothing of course. Phone restarts, still no data. I go to the settings mainly to see "phone information" and what do you know, "System Updates" is there. I click Update Profile, phone restarts, and BAM we are back online! You have no idea how happy I was! Was able to keep my phone as it was with no wipe/fresh start!
I don't know why software updates was removed in the first place! That's why I NEVER had this issue or data/call/text issues on previous phones, as I would periodically do a Profile/PRL update for good measure. Any1 know why it was removed?!? This is a vital feature to have on the phone! Mind you I never had issues, but you have no other options once you do run into an issue like this other than to do the Profile update. I don't see why they removed it, it's not bothering anything or taking up space/resources/etc. To my understanding from prior phones and years of rooting, it's standard procedure to do Profile/PRL updates from time to time to "sync/update" the phone when network/tower updates are done with Sprint.
I know this post is looong, but I literally spent from 3:30pm to 1:30am this Sunday talking to Sprint, flashing, backing up, researching. I was beyond pissed as the hrs went by with no solution on hand(I did NOT want to start fresh). This is my first post ever and my first time becoming a member for this reason. This issue is rare as I never, ever had an issue like this, but if any1 else out there runs into it, I hope they find this thread!

Related

[Q] Numerous ROM issues.

I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
The last link you put up is a theme, not a Rom. Which ROM are you currently using?
Be sure when changing roms to wipe data and cache. Not doing so will cause a boot loop, which you described above. Also, if you have to reactivate your phone and can't get a dial pad, long press the menu button to bring up the keyboard and use the keyboard numbers.
Sent from my ultra fast Liberated Droid 2
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
I don't know what all roms you have tried that won't boot but there was one person who's phones could not boot my cfsv6 through cfsv8 kernels. I fixed the issue in cfsv9 kernel so check to see if the roms you have tried are using those kernels. I know the one you said booted was an older rom and was not using my kernel. CELBFroyo is using the v9 kernel if you want to test that. If that is your issue you can just download the cfsv9 kernel and flash it after flashing the rom of your choice. It was something to do with the hardware in a small percentage of eris's that the kernel would not work with. Maybe you have the same hardware as that case...

[Q] Suddenly not getting any signal at all for no discernible reason

Ok, so here's the scoop.
Earlier today for no reason that I can pinpoint I lost all Cellular connectivity on my photon while at work. No calling, no 3G, etc. I figured it was just a hiccup or possibly that they where working on the towers in my area and that it would eventually just come back up.
That was over 12 hours ago, and I have already traveled from work, to home and still no change.
I began to think that maybe my PRL was out of date, so I flashed back to a blur based Rom that has worked for me in the past (I normally use CWM7.2 and moved to Imperium_Initiative_v1.0.5 to try and do this) and tried to initiate the update there.
Still, no results. Not only would the PRL & profile not update but I got a general "NETWORK_ERROR" every time I attempted to do so.
I'm getting a little desperate because I really need to have my phone active for work and other reasons.
I've already restored old NAND backups, restarted the phone numerous times, and so far nothing is working...
If it is indeed a PRL issue, is there a way to manually flash an updated version onto the phone?
Any help that anyone can offer is greatly appreciated!
-Timboman
P.S. The only major change that has been made to the phone recently was I purchased a new extended battery about a month back. It's been working great since I broke it in, and have no so much as flashed a new rom image since I got it. It's the Trexcell Motorola Photon 3570mah Extended Battery.
Well I decided to bite the bullet and do a full re-lock and stock re-flash and I now have gotten my signal back.
Still have no idea why it happened to begin with, but I have apparently solved my issue.
If anyone can give me a reason this might have happened then at least this topic can be of future use to someone else.
-Timboman
Timboman said:
Well I decided to bite the bullet and do a full re-lock and stock re-flash and I now have gotten my signal back.
Still have no idea why it happened to begin with, but I have apparently solved my issue.
If anyone can give me a reason this might have happened then at least this topic can be of future use to someone else.
-Timboman
Click to expand...
Click to collapse
This happened to me once while on cm7, again, for no apparent reason. After being baffled for an hour i got pissed and went to bed thinking my radio died. Signal was back by morning. Id be willing to bet yours would have come back too. Pawn it off as a hiccup and keep flashin stuffs.
Sent from my MB855 using XDA

Help me figure out why....

I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
flyinjoe13 said:
I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
Click to expand...
Click to collapse
There are some versions that lose connectivity/data connection but it's not a borked radio. Most of the time you can restore a working system by just turning off data for a minute and then turning it back on.
I am in the process of downloading the "stable" release from 2013-12-11, but my current nightly of 2013-12-10 hasn't had any hiccups.
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
flyinjoe13 said:
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
Click to expand...
Click to collapse
Ahhh, the 000-000-0000 number. Seriously, pull the battery. Don't shutdown, just pull it out, reseat, and turn on.
BTW, I installed the stable version yesterday and haven't had any problems. Flawless install, all of my apps still work and I didn't lose any data.
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Have you tried running the latest RUU then flashing recovery and restoring? That seemed to solve a random reboot issue I was having, although I've never had radio issues. I have dirtyracun s-off, so it was pretty quick and easy.
flyinjoe13 said:
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Click to expand...
Click to collapse
Do you have system select as automatic or home only? I have that issue when automatic is selected.
Sent from my ADR6425LVW using Tapatalk
I tried both automatic and home with same results. At some point i'll give it another try, but for now i'm going to stick with the Venom ROM because i'm getting tired of having to reset the radio. Some cold winter weekend day when i'm stuck in the house, i'll give it another shot.

[Q] Please Help Me: Rooted Phone & Weirdness After Factory Reset & Failed ROM Flash

[Q] Please Help Me: Rooted Phone & Weirdness After Factory Reset & Failed ROM Flash
So I rooted my SGS4 a few months after getting it from VZW. I was fine with it simply being rooted for over a year and finally decided there was a few things I no longer wanted to live with. I started going down the path of flashing a ROM and after what I felt was enough research settled on the one that would work with my phone. Or so I thought. Short story is it did not and I found out later it wasn't compatible. Prior to flashing said ROM I created a backup and did a factory reset and wipe like a good little boy. Well, I think this is what caused the issues I'm now experiencing. I'll start with the few I can think or right off-hand as being the man annoyances but I reserve the right to add more later as they come up.
So, w/o further adieu, here's the issues I'm having, numbered for our convenience.
1) Whenever I boot up my phone I get the 'Android is Upgrading' after every single reboot with about 62 items 'upgrading' so it takes a while. I use my phone a lot and carry spare batteries that I change out every time it gets low so this can be several times a day and many times the wait of several minutes is quite inconvenient. As I found in a search, I tried using an app called 'Lucky AppManager' to clear the ODEX files and it reboots and I do it again a few times and it still doesn't seem to do any good.
2) for some reason all of my contacts has a little SIM card next to them that I don't recall seeing and it now won't let me edit any of them to add or remove information. This is annoying.
3) This one had been going on for a bit prior to me attempting to flash a ROM so I had hoped at minimum it would be resolved after the reset. Nope. Power down times are very slow. It used to be whenever I powered it down it took only a dozen or so seconds. Even less right when I got it. Then, one day, it took a minute or two to completely power down and has taken that long every since. Annoying.
There was something else but as I type this I'm drawing a blank. Any help that anyone can help me on any of the above would greatly help me.
Thanks!
p.s. This is a duplicate thread since I was so rudely made aware that I had posted to the wrong subforum. Sometimes this forum earns is rep. Sorry to those who genuinely care because a few bad apples ruin it for everyone.
OstrichSak said:
So I rooted my SGS4 a few months after getting it from VZW. I was fine with it simply being rooted for over a year and finally decided there was a few things I no longer wanted to live with. I started going down the path of flashing a ROM and after what I felt was enough research settled on the one that would work with my phone. Or so I thought. Short story is it did not and I found out later it wasn't compatible. Prior to flashing said ROM I created a backup and did a factory reset and wipe like a good little boy. Well, I think this is what caused the issues I'm now experiencing. I'll start with the few I can think or right off-hand as being the man annoyances but I reserve the right to add more later as they come up.
So, w/o further adieu, here's the issues I'm having, numbered for our convenience.
1) Whenever I boot up my phone I get the 'Android is Upgrading' after every single reboot with about 62 items 'upgrading' so it takes a while. I use my phone a lot and carry spare batteries that I change out every time it gets low so this can be several times a day and many times the wait of several minutes is quite inconvenient. As I found in a search, I tried using an app called 'Lucky AppManager' to clear the ODEX files and it reboots and I do it again a few times and it still doesn't seem to do any good.
2) for some reason all of my contacts has a little SIM card next to them that I don't recall seeing and it now won't let me edit any of them to add or remove information. This is annoying.
3) This one had been going on for a bit prior to me attempting to flash a ROM so I had hoped at minimum it would be resolved after the reset. Nope. Power down times are very slow. It used to be whenever I powered it down it took only a dozen or so seconds. Even less right when I got it. Then, one day, it took a minute or two to completely power down and has taken that long every since. Annoying.
There was something else but as I type this I'm drawing a blank. Any help that anyone can help me on any of the above would greatly help me.
Thanks!
p.s. This is a duplicate thread since I was so rudely made aware that I had posted to the wrong subforum. Sometimes this forum earns is rep. Sorry to those who genuinely care because a few bad apples ruin it for everyone.
Click to expand...
Click to collapse
If you're on nk1 or ng6, have you tried going back to nc5 via odin? It sounds like you need to flash the full wipe nc5 and start over from scratch.

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