I flashed CM 10.1 (CDMA version) the other day and since then, phone calls haven't really worked. I can make outbound calls, but can't really receive inbound ones. When the calls connect, I can hear everything on the other line, but they can't hear me at all. I managed to reinstall Sprint Zone, and the network test shows Voice fails, and tells me I need to update my profile. The funny thing is, my data network works better than on the stock ROM.
Onto tried solutions:
CM 10.1 doesn't have a menu to update profile or prl, and the methods in the forums and on the web for manually updating PRL are way above my head. Special dialer codes like ##3282# don't work at all. Got off the phone with Sprint Customer Care this morning, and even though the lady was nice, she pretty much told me I'm SOL. If ANYONE has a solution, or at least a temporary fix for making calls, please, for the love of God reply. I'm really freaking new to this and lost all my backups somewhere along the way, so restoring it to pre-flash isn't an option.
EDIT: Finally figured out how and successfully flashed the factory FXZ for 4.1.2. Problem Solved.
You need to do any/all PRL updating before flashing a custom ROM.
Reflash stock, get everything working there - update your PRL, make sure voice works (inbound, outbound etc). Then flash a custom ROM.
Also, I recommend something newer - CM10.1 is really old at this point. CM11 is pretty stable, even the nightlies - although note, they are all built under a unified device name, look for moto_msm8960
Related
Here's an odd one. I have two HTC Evo 3D CDMA phones, both with CyanogenMod 10.1. One works perfectly fine. The other cannot place calls, send texts, or use data. When making a call, I get an automated voice that says "Error 16", and when trying to send a text, it tries for a couple minutes and eventually fails. The PRI and baseband are the same on both; the PRL is different.
I searched around a bit, and all I could find was to call Sprint. Ting is my provider, so I called them and they asked me to do a ##number# thing, which does not work with CM's dialer. Next they suggested a profile update, which is also absent in CM. I even went as far as flashing a Sense-based ROM, doing those things (at which point the phone worked fine), then re-flashing CM, but it goes back to Error 16.
Any ideas? I cannot fathom why one phone would work and one would not when everything aside from the PRL is identical. Could that be the cause? If it is, I think I'm out of luck, because for one reason or another I've never been able to change the PRL on this particular phone. I go through the process with QPST, and everything seems to go fine, but upon reboot the PRL has not changed.
Any help would be appreciated.
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
TenderloinShadow said:
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
Click to expand...
Click to collapse
Go into About Phone -> status check your IMEI and PRL and such are they still there?
buhohitr said:
Go into About Phone -> status check your IMEI and PRL and such are they still there?
Click to expand...
Click to collapse
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
TenderloinShadow said:
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
Click to expand...
Click to collapse
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
The problem i had i couldn't recieved calls. Everything worked fine..
I ended up getting new sim card then the employee dialed *73 then my fone was back in action
buhohitr said:
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
Click to expand...
Click to collapse
yeah I figured that would have to be the answer from the beginning. Have to Odin back to stock first, won't be able to do that for probably another 3-4 hours because of a work meeting that's about to start, so I figured I'd ask around.
If anyone has any other ideas, I'm open to them. Otherwise I'll reprovision tonight and report back.
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
beepea206 said:
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
Click to expand...
Click to collapse
+1
Flash back to stock, or a stock based rom with stock messaging. Try to force the message through. My messages stopped sending on aosp messaging and was persistent through rom flashes. I eventually forced it through using touchwiz messaging.
Sent from my SCH-I535 using Tapatalk 2
Hey everyone,
I have a verizon s3, rooted and currently running the latest stable CM11. Everything works, I have internet and get sms/mms, and can also make calls. However I don't receive calls from known numbers. However unknown and private numbers come through (has happened once, but I have heard of others with this issue, so I assume that's what's happening here).
I'm in Israel, so I'm guessing that may have something to do with it possibly? However when we got the phone from a friend, and I put my sim card, and set the network to global, it worked. Only have I rooted it did it stop receiving calls.
Thought? Advice?
Many thanks.
Twan313 said:
Hey everyone,
I have a verizon s3, rooted and currently running the latest stable CM11. Everything works, I have internet and get sms/mms, and can also make calls. However I don't receive calls from known numbers. However unknown and private numbers come through (has happened once, but I have heard of others with this issue, so I assume that's what's happening here).
I'm in Israel, so I'm guessing that may have something to do with it possibly? However when we got the phone from a friend, and I put my sim card, and set the network to global, it worked. Only have I rooted it did it stop receiving calls.
Thought? Advice?
Many thanks.
Click to expand...
Click to collapse
I had the same problem with CM12 and AICP rom
I solved with this
d2gsm_rilblobs.zip
instructions
1 - install clean rom
CM12 or AICP
2 - install gapss
3-install modem
d2vzw_NE1_modem.zip
4 - flash zip
d2gsm_rilblobs.zip
restart and wait
When I purchased this phone on Swappa, everything worked, with the exception of phone calls. I assumed it was a ROM issue, but I have since tried mulitiple ROMs, with no success at resolving it. The culmination came this morning when I used the LG flash tool to fully restore it to factory settings, and the problem persists. The symptoms are as follows: when trying to make a call, the dialer opens, the call tries to connect, shows "dialing" then disconects. On a very rare occaision it will successfully connect, but I have yet to observe any pattern. Everything else works, sms, data, etc, and I have replaced the SIM card to rule that out. I will post a logcat in the first comment of when it fails, and I will try to get one of when it connects for comparison, but we'll see how that goes.
Code:
[ 02-15 15:28:14.035 4864: 4874 I/CallHandlerService ]
CallHandlerService - onDisconnected: Call{mCallId=6, mState=DISCONNECTED, mDisconnectCause=ERROR_UNSPECIFIED, mCapabilities=530, mConnectTime=0, mChildCallIds=[], mGatewayNumber=null, mGatewayPackage=null, mIdentification=CallIdentification{mCallId=6, mNumber=xxxxxxxxxx, mNumberPresentation=1, mCnapName=null, mCnapNamePresentation=0, mTelephonyCallerInfo={contactNumber=, okToGetTelephonyCallerInfo=false, cachedPhotoIcon=null, phoneNumber=, person_id=0, photoResource=0, name=, contactExists=false, contactExistsCount=0, cachedPhoto=null}}, mSsNotification=null, mConnectionInfo=ConnectionInfo{mCallId=6, mAddress=xxxxxxxxxx, mOriginalNumber=xxxxxxxxxx, mCdnipNumber=null, mToa=129}, mLine1Number=xxxxxxxxxxx, mSubscription=0, mRoamingCallIsIncoming=0, mRoamingRadMode=0, mRoamingPrefix=null, mIsConfConn=0, mPrivacyKeeperState=NONE}
[ 02-15 15:28:14.035 4864: 4864 I/CallHandlerService ]
CallHandlerService - ON_DISCONNECT_CALL: Call{mCallId=6, mState=DISCONNECTED, mDisconnectCause=ERROR_UNSPECIFIED, mCapabilities=530, mConnectTime=0, mChildCallIds=[], mGatewayNumber=null, mGatewayPackage=null, mIdentification=CallIdentification{mCallId=6, mNumber=xxxxxxxxxx, mNumberPresentation=1, mCnapName=null, mCnapNamePresentation=0, mTelephonyCallerInfo={contactNumber=, okToGetTelephonyCallerInfo=false, cachedPhotoIcon=null, phoneNumber=, person_id=0, photoResource=0, name=, contactExists=false, contactExistsCount=0, cachedPhoto=null}}, mSsNotification=null, mConnectionInfo=ConnectionInfo{mCallId=6, mAddress=xxxxxxxxxx, mOriginalNumber=xxxxxxxxxx, mCdnipNumber=null, mToa=129}, mLine1Number=xxxxxxxxxxx, mSubscription=0, mRoamingCallIsIncoming=0, mRoamingRadMode=0, mRoamingPrefix=null, mIsConfConn=0, mPrivacyKeeperState=NONE}
[ 02-15 15:28:14.035 1471: 1471 D/CallNotifier ]
onDisconnect: cause = ERROR_UNSPECIFIED, incoming = false, date = 1455568080816, subscription = 0
That seems to be the most relevant series of lines from the failure logcat. Full log attached, if anyone knows what specifically to look for.
I really don't know what to look for, and the full log is too long to post, so I will attach it here.
Does anyone have any ideas what is wrong, or what I need to do to get this device to work reliably? Is it possible that it is the SIM reader? (seems unlikely since SMS and data work, and calls work intermittently.) Also worth noting, calls seem to connect immediately after a reboot fairly consistently.
Bump?
Bump x 2?
Desperation bump? LG says they can only evaluate the device if I provide a copy of the original sales reciept, which the guy I bought it from says he can't get. He guarentees the device was working when he shipped it, though I have some doubts, as he did indicate he wasn't using it, just made some test calls, and the phone seems ot work immeidately aftera reboot... Any ideas at all??
rassawyer said:
Desperation bump? LG says they can only evaluate the device if I provide a copy of the original sales reciept, which the guy I bought it from says he can't get. He guarentees the device was working when he shipped it, though I have some doubts, as he did indicate he wasn't using it, just made some test calls, and the phone seems ot work immeidately aftera reboot... Any ideas at all??
Click to expand...
Click to collapse
I don't think it's hardware. Sounds like an internal setting got messed up. I assume you've cleared everything that's clearable from recovery.
I suggest you flash CM13. If you still have the problem, ask the CM guys for help.
I have the same problem. Wife has same phone, doesn't have problem (but has software version d85021q). I am currently using sock rooted 20f, flashed 21r modem. tried different roms all have the same problem. sim works fine in my old S4. data and texts work fine. Calls try but then stop with call ended. problems with receiving calls too. Signal strength is -108db same as hers, the S4 is about the same maybe -106db. here's a list I have tried.
1. stock KK rom
2. stock rooted 20f rom
3. RR 5.5.8 rom
4. fulmics 2.7 rom
5. latest cm 12.1 nightly
6. flashed 20f modem
7. flashed 21r modem
I would try flashing MM roms but without the baseband updates would I be in the same boat? Also worried about being stuck with MM if I want to return to LP.
I did pretty much everything possible to try to resolve this, with not success. I tried multiple custom roms, I used the LG Flash Tool to try multiple version of factory rom, and never had any luck. Always the same issue, everything worked but phone calls. I gave up, and bought a device with a shattered screen, and swapped the board over into my good body. Of anyone comes up with any ideas, I'm very interested. I have the equipment to even do on board repairs/component replacements, but I don't know what to try to replace, since the radio obviously works or data and texts wouldn't work.
I've tried pretty much everything imaginable from a software/firmware standpoint... I've tried multiple custom ROMs, I've used the LG Flash Tool to flash multiple version of stock, and multiple modems, etc. I always ended up with the same result. Everything worked but phone calls. I finally gave up and bought a device with a smashed screen, and swapped that board into my body. I'd still be interested if anyone has any insights. I have the equipment necessary to replace board level components, etc, but I don't have the equipment to test them, so I don't know what to try replacing. The radio is obviously functional, since text + data work...
First, I don't know much about custom ROMs or root processes in general. I rooted the phone myself, and installed the recovery/flashed the ROMs, but my knowledge is one step above basic, if that.
A couple of weeks ago I stopped being able to send MMS. I simply dealt with it. I don't send a whole lot of pictures. I finally called Sprint yesterday to address the issue, and the wizard on the other side of the line did some sort of magical spell which caused (I think, could've been coincidence) my 3G connection to stop functioning as well after a few reboots.
This is a Samsung Galaxy S3 for the Sprint network. I am currently running CyanogenMod 11 (AV 4.4.4) and have ClockWorkMod installed as my recovery. Fixes I have tried so far include:
- Reflashing all my ROMs
- Updating CM11
- Flashing CM12.1 instead of CM11
- Multiple hard/soft reboots
- TouchWiz MMS Fix
- FreedomPop APN adjustment
Nothing has worked so far. I am at the point where I am about to just purchase a new phone. If it matters, the verdict on the phone with Sprint was to take it to a store, which I did, but when they crack open an AOSP it seems they have no idea what they're doing.
Please help.
zmauls said:
First, I don't know much about custom ROMs or root processes in general. I rooted the phone myself, and installed the recovery/flashed the ROMs, but my knowledge is one step above basic, if that.
A couple of weeks ago I stopped being able to send MMS. I simply dealt with it. I don't send a whole lot of pictures. I finally called Sprint yesterday to address the issue, and the wizard on the other side of the line did some sort of magical spell which caused (I think, could've been coincidence) my 3G connection to stop functioning as well after a few reboots.
This is a Samsung Galaxy S3 for the Sprint network. I am currently running CyanogenMod 11 (AV 4.4.4) and have ClockWorkMod installed as my recovery. Fixes I have tried so far include:
- Reflashing all my ROMs
- Updating CM11
- Flashing CM12.1 instead of CM11
- Multiple hard/soft reboots
- TouchWiz MMS Fix
- FreedomPop APN adjustment
Nothing has worked so far. I am at the point where I am about to just purchase a new phone. If it matters, the verdict on the phone with Sprint was to take it to a store, which I did, but when they crack open an AOSP it seems they have no idea what they're doing.
Please help.
Click to expand...
Click to collapse
This issue has been resolved. I flashed over a rooted stock MK3 ROM with a custom modem which allowed me to update profile and PRL. Thank you.
Great that you solved the problem.