[Q] SMS won't send. Can receive/send MMS calls and Data

[Whisk_33]

The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.

What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue

Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM

The Solution

Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.

NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)

Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.

Requirements:

• A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
• VRBMB1 AIO Flash, available here. (Thread here.)
• I'm going to assume you know how to boot into and use recovery.

NOTE: Do NOT let the stock ROM install any updates.

1. Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
2. Flash the VRBMB1 AIO.
3. Wipe data and cache.
4. Flash the stock ROM.
5. Boot into the stock ROM.
6. The reprovisioning seems to happen as a part of ROM's initial boot up.
7. Send a few text messages to test. (I sent them to Twitter.)
8. Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
9. This would be a good time to back up your IMEI if you haven't already done so.
10. Reboot into your recovery, wipe data/cache and restore your nandroid backup.

At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.

DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!

CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)

I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip

Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.

 

[jugsins]

This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.

Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.


Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already

 

[Whisk_33]

It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822

It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...

Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.

edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899

 

[S52Stu]

Just looking for more info

Sent from my SCH-I535 using Tapatalk

 

[Whisk_33]

Just looking for more info

Sent from my SCH-I535 using Tapatalk

SO this is the current status that I know.

The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).

Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code

I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.

 

[S52Stu]

I'm 717

Sent from my SCH-I535 using Tapatalk

 

[Whisk_33]

I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.

And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.

 

[S52Stu]

I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?

Sent from my SCH-I535 using Tapatalk

 

[DreamFX]

Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658

 

[Whisk_33]

Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658

Godspeed my friend.

 

[DreamFX]

Anyone try aosp to see if fixed yet?

 

[capt730]

Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.

 

[DreamFX]

Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.

I try every other day. 717 for me. Remaining hopeful it's fixed... One day...

 

[capt730]

What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.

Sent from my GT-N5110 using XDA Premium 4 mobile app

 

[Obaterista93]

What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.

Sent from my GT-N5110 using XDA Premium 4 mobile app

It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.

Sent from my SCH-I535 using XDA Premium 4 mobile app

 

[capt730]

I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.

*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.

 

[Obaterista93]

I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.

*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.

It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.

 

[capt730]

I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.

 

[Whisk_33]

It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.

I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.

I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,

 

[Obaterista93]

I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.

I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,

Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.