Jump to content

Galaxy S3 goes into a reboot loop or loses signal when connected to a certain tower


MaxPower

Recommended Posts

I'm running a custom ROM and it had been working great until all of a sudden the phone started rebooting constantly but only when I was home. I've found that if I swtich the network mode to CDMA only, the phone is stable and works great. Switching to CDMA/LTE throws the phone into an endless reboot loop of causes the signal to be lost, depending on which kernel I have flashed. I have the MK3 modem flashed and I've flashed it several times, I've done a complete wipe of the phone and reflashed the ROM, nothing helps. Having the WiFi on or off makes no difference.

 

Could the problem be hardware related? Does it have something to do with the tower and if it does, will it go away at some point? I tried asking in the ROM's thread at XDA but no one seems to know exactly what's going on.

 

This only happens when I'm home or close to home and in CDMA/LTE mode.

Link to comment
Share on other sites

Have you tried ODINing completely back to stock?

 

I don't remember whether or not the GS3 had a separate LTE modem firmware from CDMA, but it likely does. I'd try flashing a couple modems back, in succession, up to the latest.

 

You haven't mentioned whether or not the device connects normally to EHRPD or LTE, only that being in LTE mode freaks it out.

  • Like 1
Link to comment
Share on other sites

Have you tried ODINing completely back to stock?

 

I don't remember whether or not the GS3 had a separate LTE modem firmware from CDMA, but it likely does. I'd try flashing a couple modems back, in succession, up to the latest.

 

You haven't mentioned whether or not the device connects normally to EHRPD or LTE, only that being in LTE mode freaks it out.

 I flashed MB1, MD4, then MK3 but that didn't help. Right now I have it in CDMA/LTE mode and it's connected to CDMA eHRPD, every once in a while I will lose signal and regain it, I assume this is when it tries to connect to LTE. I will try to do another hands free activation later today when the phone has no problems connecting to LTE.

 

I haven't tried ODIN to stock, I will do that this weekend if everything else fails.

Link to comment
Share on other sites

Happened to me running MOAR ROM a little less than a year ago. Anytime I was in SFO and it would try to connect to LTE, it would reboot. Found out it was a kernel problem, but I elected to go to Cynaogen Mod and have had no issues since with the stock kernel that installs with it. I tried multiple modem flashes, none worked. Radio update didn't work, either. Look into other kernels, or other ROMs to fix it. 

If you haven't tried CM, I'd highly recommend it, just stay away from the KitKat builds for now. I'm running 10.2 stable and it's great.

Link to comment
Share on other sites

I flashed CM10 and went back to stock, didn't help. It keeps connecting to Sprint's network then disconnecting constantly. There's no more stable connection but only when I'm home or nearby. I don't think there's anything else I can do that software related so now my question is, will a Sprint repair center even look at the phone if it's over a year old? There's no repair center near me so they aren't going to be able to duplicate the problem so maybe there's no point and I should just wait it out to see if it resolves itself as sudden as it broke or if I should just replace it.

Link to comment
Share on other sites

I got into some trouble screwing with some settings deep in the hidden menus on stock. Eventually, I had zero connectivity on mobile. Took it to a Sprint store, and they fixed it in 5 mins. This was when the phone was about 15 months old.

 

Sent from my SPH-L710 using Tapatalk

 

 

Link to comment
Share on other sites

I got into some trouble screwing with some settings deep in the hidden menus on stock. Eventually, I had zero connectivity on mobile. Took it to a Sprint store, and they fixed it in 5 mins. This was when the phone was about 15 months old.

 

Sent from my SPH-L710 using Tapatalk

 

I'll flash stock back on there and take it to them tomorrow. I wish they could see it disconnecting but oh well.

Link to comment
Share on other sites

I got into some trouble screwing with some settings deep in the hidden menus on stock. Eventually, I had zero connectivity on mobile.

 

If in a hidden menu you ever see "Korea mode" -- I still have not determined what it is -- do not select it.  I learned the hard way some years ago.

 

AJ

  • Like 1
Link to comment
Share on other sites

I took it to the Sprint repair center and they said nothing is wrong with the phone, that they've been doing lots of tower upgrades and to give it a couple of days and it might start working again. It's not the tower because there are other phones on my account that connect just fine, that didn't matter to them though.

 

Doing more research I found this thread: https://community.sprint.com/baw/thread/90885

 

My problem started happening when the battery on the phone died. I didn't think it had anything to do with it but now it looks like it does. Of course, I've already tried everything mentioned there x20. There are several more repair centers in the area, there has to be a tech at one of them that knows what's going on...

Link to comment
Share on other sites

  • 2 weeks later...

The same thing is happening to another S3 on a different account. Mine is rooted, the other isn't. Both running 4.3 but I flashed 4.1 on mine with no resolution. It seems like certain S3s don't like certain Sprint towers.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • As far as I know it's ubiquitous. Ultimately the network decides if you should use VoNR vs VoLTE but pretty much anytime my phone is in standalone mode and I place a call, it goes over NR.   Yup, it was terrible. After a while, I just connected to the WiFi, and that worked fine at about 90Mbps. I get the feeling that rather than doing a "real" upgrade where they install new antennas, upgrade backhaul, etc., T-Mobile instead installed new radios onto the existing and already overloaded DAS and called it a day, which isn't enough. Compared to Yankee Stadium, where they actually went and deployed new antennas/radios for their n41 upgrade, and you're able to get upwards of 200Mbps at sold-out games, Arthur Ashe really is a joke. What's worse is that the folks in their NOC likely know this already, but no effort is being made to change that. I'm not asking for T-Mobile to deploy mmWave everywhere like Verizon but there is a real use case for it at stadiums.
    • Does anyone know how well implemented is VoNR in the 5 boroughs. Does anyone use it? I have an iPhone 15 Pro. Does anyone know if T-Mobile is still working on upgrading their network? It seems like the service has gone down. My phone struggles in parts of the Belt Pkwy, and data is slow. 
    • I come to the US Open men’s semifinals and finals every year, and I’ve never been able to use my T-Mobile phone successfully. Usually AT&T is the top performer—good to hear Verizon has upped their game. 
    • One sector down, two more to go — — — — —  I was at Arthur Ashe Stadium for the U.S. Open today and the good news is that there is an n25/41 DAS setup throughout USTA Billie Jean King National Tennis Center. From the "boardwalk" to the outdoor concession area, to inside the stadium; you connect to standalone n41 and n25 everywhere via oDAS and iDAS. The bad news is that in the actual stadium it's beyond useless. While I saw strong coverage as indicated by signal bars and I was able to make calls and send texts, there was no data throughput at all. Running a speed test failed 9 out of 10 times. The only time I got a speed test to work was by switching to LTE funnily enough or by using NSA 5G where the test would initiate via LTE and then n41 would kick in giving me ~20Mbps. T-Mobile has so much traffic on their 5G network that now n41 gets bogged down before LTE. That was a first for me! In the stadium in the same area Verizon got 1.2Gbps on mmWave and LTE kept timing out when trying to test it. My Boost line on AT&T got upwards of 150Mbps on C-band and I know they have mmWave deployed as I saw their Nokia mmWave antennas deployed but I was unable to test it. In the outdoor concession area T-Mobile performed well getting over 150Mbps on n41. AT&T in these areas saw over 250Mbps on C-band and I didn't get the opportunity to test Verizon there. It just seems like 140MHz n41 is not enough capacity for the amount of people inside the stadium. Hopefully T-Mobile is considering deploying n258 to all of these stadiums since they now own that mmWave nationwide. It'd make a world of difference in terms of capacity at these venues. Bonus Pics: Verizon and AT&T mmWave Hidden carrier neutral DAS: 
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...