SOLVED: CM13.0 Nightly - No LTE - Sprint Galaxy S 5 Q&A, Help & Troubleshooting

I have been using the CM13 nightlies for a few days now, and all I can say is wow - I love it! Phone is super fast, no more constant freezing and restarting (when I was on MOAR rom).
Only problem I've had so far is that I cannot connect to 4G LTE network. I have Boost Mobile and the default Boost APN seems to work fine, I can connect to 3G if I set the preferred network type to 3G, but when I set it to LTE I get neither 3G or 4G LTE. I do not know whether I should be using NV or RUIM/SIM in CDMA subscription (and couldn't figure it out through googling either) but it seems that I cannot change it to RUIM/SIM, no matter how many times I click the option it just stays on NV. Also, trying to open carrier settings just crashes settings "com.android.phone has stopped"
SIM status shows network state as disconnected when I have LTE or Global chosen as preferred network state.
I started out with the unofficial CM13 build, then from there upgraded to the 20160716 official nightly and then the 20160720 nightly.
I then flashed a stock 6.0 rom I found here and that let me connect to 4G with no problems whatsoever. While in this rom, I updated my PRL just in case. I then flashed back the 20160720 official nightly, and same thing. Still no dice.
TL;DR anyone have 4g working on boost with cm13

update:
found this flashable zip through google, flashed it in TWRP and LTE has worked like a charm ever since. :good:

Related

[Q] Lost 3G Data on Cricket. Can anyone help?

I currently flashed and activated the Epic 4g (Sph-D700) on the cricket network, and everything was working good. But stupidly I flashed the Cyanogenmod 7 RC3 for the Epic 4g on Sprint network thinking the 3g would work. But ever since then I could never get the 3g working anymore.
Tried many steps; from QPST, APN settings, returning to stock, flashing CM9 Beta 4 on cricket, CM7 for Cricket, trying many ways in many forums to fix 3g, and returning to Cyanognemod 7 RC3 on Sprint and trying to fix it from there.
don't know what to do anymore. I installed an app like root explorer for free and messed with the apn. Tried to mess with the hap secret going to system, etc and reaching ppp. Tried installing the epic 4g different cell phone company fix flash file, the i905 data fix and no luck. I tried using CDMA workshop and QPST and tried a bunch of PRLs and the 3g icon wouldn't even pop up.
The PRL that worked with 3g cricket was 42700 one. Flash cyanogenmod 7 screwed it up. I even used voice dials to open APN and nothing. Even dialed ##8778# and set it back to PDA. Tried dialing #data and mess the settings there. Does anyone have a back up of the apn settings on cricket where the 3g works? I currently have thr $55 plan .
I noticed that on cm7 and cm9 the connection goes to 1x and no 3g connection. Also noticed that I keep losing signal and sounds like its updating PRL.
If anyone can help, please

Flashed latest cm10 nightly and messed with some settings - 3g now lost(lte works)

I just updated to the 9/7 official nightly and messed with some settings (trying to get mms working).
Right now, if I set myself into 3g mode, I don't get any data. 4g still works.
I was doing the old mms fix where I changed the CDMA subscription to NV from RUIM/SIM and back. I still have a phone number and an IMEI, but if I switch to CDMA mode, no data.
I prefer to use 3g for battery savings, and also, I don't always get 4g coverage, so it would be nice to fix. Any ideas?
I'm not sure if it was the flash or the messing-around that caused the problem because right after flashing I was on WiFi and didn't notice if 3g still worked.

SCH-I535 no LTE but 3G and Cell service works

Hi all, I have a bit of an issue that I can't seem to resolve. Currently running CM10.1 RC5.
LTE does not work, 3G is fine. After some research I decided to do a factory wipe and reload Cm10.1 RC5, no positive results. Then upgraded the baseband to I535VRBMB1 from I535VRLG1 with no positive results.
I verified Network Mode is set to LTE/CDMA/EvDo, System select is Home Only and CDMA subscription is RUIM/SIM.
I found out that if I change the CDMA subscription to NV, LTE will activate and work properly but cell service does not work. I verified this with wireless disabled and used a Speedtest application with results of 61 ms, 5441 down and 6260 up.
This issue occurred as of RC1. One other item to note is I attempted an update by dialing *228 and pressing 2.
My network provider is Verizon Wireless.
Any assistance is greatly appreciated.
jobless said:
LTE does not work, 3G is fine. After some research I decided to do a factory wipe and reload Cm10.1 RC5, no positive results. Then upgraded the baseband to I535VRBMB1 from I535VRLG1 with no positive results..
Click to expand...
Click to collapse
Fixed. I followed this procedure http://forum.xda-developers.com/showthread.php?t=1974114 to bring my phone back to stock, rooted w/recovery and VRBMB1. Wiped data, cache and davlik in recovery. Booted up and did not sync any content. Called Verizon Wireless and had them reprovision my SIM card. The tech told me turn off the phone and he pushed out updated roaming and updated tower information to my phone. Booted up and after ~6 minutes 4G activated.
I have since installed CM 10.1 RC5, synced with my apps and data, and I have maintained 4G service since.
If you have a 4G phone with Verizon Wireless, do not attempt to update roaming/cell tower info by calling *228. Instead call Verizon and have them push the updated info to your phone.

No more 4G

So the issue I have is I no longer have 4G. I got off an airplane and my phone had no 3G or 4G service. If I rebooted my phone or turned airplane mode off and on I would get 4G service for about 2 mins before it would switch back to 1x. Below is what I have done to try and fix the problem. Any ideas on what else I can do.
Reloaded a nightly of CM11. Did not fix anything.
Used odin to load a stock TW 4.04 rom. (still no 3g or 4g service)
Noticed that my IMEI had been earased to 0. I went to a verizon store to check my SIM card and noticed it was gone.
Used MTK NVram to restore my IMEI. (Still no 3g or 4g service)
Used the terminal command SU REBOOT NVrestore (This gave me back 3g service but I still do not have 4G service.)
I've search everywhere and cannot find a solution. Any help would be appreciated. I currently switch between CM11 and TW4.4 rom. Neither connect and preferred network is set to LTE, switching to global makes no change.
Thanks

Can't connect to AT&T LTE APNs with custom ROMs

I have a 32GB US version Nexus 5 which up until today has been totally factory, updated to the final 6.0.0 release from Google. Today I installed the latest official releases of TWRP, then LineageOS (with OpenGApps nano) and ran into no issues until I got LineageOS up and discovered that mobile data didn't work. This is using the same AT&T SIM which previously worked fine. I checked in the Access Point Names menu and determined that some APNs which are included but not selected will allow me to connect using 3G but none will allow LTE. APNs which should allow LTE, even one that I create myself using parameters from AT&T's website, do not connect at all; I can see signal strength, but no data connection is made as if I had Wi-Fi active even when it is disabled. If I use the "Bearer" field to specify that I want to allow only LTE, the entry I am editing disappears entirely from the menu after being saved. LTE is set as the preferred network type in mobile network settings by default, and I haven't changed it.
I tried swapping the AT&T SIM with a Google Fi SIM I had on hand and the Google SIM worked fine with LTE, but unfortunately I'm intending to use this phone with AT&T.
After having no success with LineageOS I wanted to rule out issues with the specific image being used, so I reflashed using Resurrection Remix based on 8.1 instead of 7.1 like Lineage. However, this made no difference - I can still connect with 3G but not LTE. Since I've upgraded three other phones to Lineage and never seen a similar issue, I am a bit mystified. Is this a known issue with the Nexus 5 that requires some sort of workaround, or do I have something odd going on?

Categories

Resources