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

22nd February 2014, 02:20 PM | #1

OP Senior Member

Scranton

Thanks Meter: 29

103 posts

Join Date:Joined: Dec 2012

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

Quote:

Originally Posted by net-cat

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.

Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
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.
This would be a good time to back up your IMEI if you haven't already done so.
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.)

Quote:

Originally Posted by buffal0b1ll

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/7b1aqspo40...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.

Last edited by Whisk_33; 8th May 2014 at 02:54 PM. Reason: Updating temp down links

The Following 7 Users Say Thank You to Whisk_33 For This Useful Post: [ View ]

23rd February 2014, 03:19 AM | #2

Junior Member

Thanks Meter: 0

1 posts

Join Date:Joined: Feb 2014

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

23rd February 2014, 07:27 PM | #3

OP Senior Member

Scranton

Thanks Meter: 29

103 posts

Join Date:Joined: Dec 2012

It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/show....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/show....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/show...php?p=50627899

Last edited by Whisk_33; 25th February 2014 at 08:06 PM.

25th February 2014, 03:27 AM | #4

Senior Member

Thanks Meter: 30

283 posts

Join Date:Joined: Apr 2012

Just looking for more info

Sent from my SCH-I535 using Tapatalk

26th February 2014, 03:17 PM | #5

OP Senior Member

Scranton

Thanks Meter: 29

103 posts

Join Date:Joined: Dec 2012

Quote:

Originally Posted by Dex954

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.

Last edited by Whisk_33; 26th February 2014 at 05:37 PM.

26th February 2014, 03:40 PM | #6

Senior Member

Thanks Meter: 30

283 posts

Join Date:Joined: Apr 2012

I'm 717

Sent from my SCH-I535 using Tapatalk

28th February 2014, 01:16 PM | #7

OP Senior Member

Scranton

Thanks Meter: 29

103 posts

Join Date:Joined: Dec 2012

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.

28th February 2014, 02:00 PM | #8

Senior Member

Thanks Meter: 30

283 posts

Join Date:Joined: Apr 2012

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

28th February 2014, 02:57 PM | #9

Senior Member

Thanks Meter: 433

1,267 posts

Join Date:Joined: Jan 2011

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/show....php?t=2662658

28th February 2014, 05:42 PM | #10

OP Senior Member

Scranton

Thanks Meter: 29

103 posts

Join Date:Joined: Dec 2012

Quote:

Originally Posted by 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/show....php?t=2662658

Godspeed my friend.

The Following User Says Thank You to Whisk_33 For This Useful Post: [ View ]