yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] S52Stu:
That's why I think this is going to be a hard road..
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
This is actually quite fascinating. All of those who seem to be having this issue are in Central Pennsylvania, started having the issue around the 20th, and are running a version of Cyanogenmod. I'll be sure to bring that up in my next chat with Verizon. Stay posted.
[Verizon Samsung Galaxy S III] barakaspeed:
Hershey PA here

Cm11 m3 d2vzw

I've been having the same problem since ~20th as well. In glad I found this thread as I couldn't find much else when searching. I've temporarily switched to a TW ROM and it worked fine but any aosp seems affected. I even got Verizon to give me a sim but it didn't help.

My cell number starts 570-57*-**** (Scranton area number ) though I now live in Hershey pa.
[Verizon Samsung Galaxy S III] S52Stu:
This is where I wish I knew someone who worked at vzw and was a reasonable person.
[Verizon Samsung Galaxy S III] bass0324:
I am just outside Philly, I started having this issue on the 20th as well, occurred on both paranoid android beta 4 from notta and slim kat stable 3.0. Seems to be intermittent for me as there is times where it works freely and times I need to toggle airplane mode for every text

Edit: my number is from northeast pa (Hazleton Area). I'm wondering if it is an area code issue or something because I know people with s3s down by philly who don't have this issue with Verizon.
[Verizon Samsung Galaxy S III] thejudgement223:
Been having the same issue. I live in mountaintop so maybe you're right
[Verizon Samsung Galaxy S III] Obaterista93:
Central PA 570 here as well. Both my mom and I's phones are experiencing the same. What baffles me is that it happened to be people who had already flashed the ROM prior to the 20th, which means it isn't an AOSP specific SIM activation issue, because that happens on first boot. Touchwiz works fine, although I can't stand it. Whatever it is, I desperately hope it's fixed soon.
[Verizon Samsung Galaxy S III] ihadacatonce:
dammit. I thought I broke my phone on the 21st when I was tinkering with dialer codes. didn't know there was a full blown conspiracy.

Lucky for y'all I have the solution (which was partially mentioned earlier):

Go into Testing (*#*#4636#*#* in the dialer). Refresh your SMSC, erase the last last 3 digits and the comma and add a plus sign after the first quotation mark. It should read

"+13123149810"

. Push update, turn radio off and back on. Not only have you restored your SMS, but you'll have access to MMS now as well.

On a side note, I noticed my GPRS is connecting successfully. This crisis was a blessing in disguise.
[Verizon Samsung Galaxy S III] tonybahr:
I'm about an hour and a half north of Scranton! Mine suddenly started working. Been fine for 2 days now. Anyone else?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
I'm still having the issue, Verizon is supposed to call me tonight, so hopefully we will get somewhere.
[Verizon Samsung Galaxy S III] tonybahr:
Oh in also on baseband vrlg1 I think its the one this phone shipped with not sure , iseem to get better signal so I'm not changing it. It may or may not have anything to do with the SMS problem. More than likely not.
[Verizon Samsung Galaxy S III] hootyburra:
Same issue in Central PA. Bloomsburg area.

Started around the 20th running Carbon d2lte nightlies, still happening on 2/25 d2vzw build.

The airplane mode trick works. I have tried various network settings, lost 4G and can't get that back either.

Can anyone share the correct network settings?
[Verizon Samsung Galaxy S III] djdmbrwsk:
Here's another thread on the same issue where I posted a temp fix...involves switching to CDMA only mode...

http://xdaforums.com/showthread.php?t=2654822

Texting Issue with CM 11.0 Nightly
[Verizon Samsung Galaxy S III] DreamFX:
We all need to call there is def something wrong with central pa / northeastern PA. Here is my thread on this issue http://xdaforums.com/showthread.php?t=2662658
[Verizon Samsung Galaxy S III] S52Stu:
I have called the problem is they tell you to take your phone to the store. You can't do that running cm.
[Verizon Samsung Galaxy S III] DreamFX:
It's not a phone issue. If it was we all wouldn't be having it.
[Verizon Samsung Galaxy S III] S52Stu:
Couldn't agree more. Verizon doesn't see it that way because they can't replicate it. As any IT outage you must replicate it. And the 20 people running cm that ARE actually calling is not replicating it. So they tell you to take it in.
[Verizon Samsung Galaxy S III] DreamFX:
This is bizzare and if I weren't apart of the issue I wouldn't believe it. I been doing this stuff for a long time and never have a had a issue where phones start refusing to send texts on aosp and not stock/tw.
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Talked to the Verizon guy again yesterday. He says that he knows many in PA are having this issue. He also knows we're using custom roms, but he's still trying to help, so that's good. He said he has network engineers working on it and they he'll call me again today. Hopefully they can fix this soon.
[Verizon Samsung Galaxy S III] S52Stu:
You got much farther than me. Props.
[Verizon Samsung Galaxy S III] DreamFX:
Please update us. If your buddy can't help I'll contact Bill Foshay

President, Northeast Area. He has helped get men in the right place to fix issues for me in the past.
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
He called me around 4 yesterday (Eastern Standard Time) so I'm expecting him to call soon. As soon as I have any info I'll share it with you guys. Really hoping for a fix soon.
[Verizon Samsung Galaxy S III] DreamFX:
Did he ever call?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
He never called. :(
[Verizon Samsung Galaxy S III] twistedillutions:
Hope u ppl get ur stuff up and running properly soon..
[Verizon Samsung Galaxy S III] DreamFX:
Me too running touch whiz Stinks :(
[Verizon Samsung Galaxy S III] DreamFX:
Issue not fixed as of today
[Verizon Samsung Galaxy S III] djdmbrwsk:
I was told I would get a call after doing an online chat with them. It sounded odd and sure enough he never called. There was however a ticket created because I got an email confirming its creation...we'll see...
[Verizon Samsung Galaxy S III] DreamFX:
How did you word your issue because I'm going to get a ticket going too?
[Verizon Samsung Galaxy S III] capt730:
I am on CR8 and having intermittent issues where messages won't send. It's been horrible today. I can send one message and then they just fail after that. I live on the West Shore and work in York. Toggling data doesn't do anything - have to reboot to send.

Since I haven't been on AOSP since 4.3 rolled out, I would think that there is something more going on here.
[Verizon Samsung Galaxy S III] DreamFX:
I would call in to report the more people that do the greater chance of getting this resolved.
[Verizon Samsung Galaxy S III] djdmbrwsk:
I wouldn't mention anything about a custom ROM since they probably won't help you if you do...and honestly I don't think it has anything to do with the ROM. Just tell them the symptoms and even say you have a local friend who has the same issue with a different phone so they see it as a network issue vs a device issue.
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Apologies for the lack of communication on this forum for the past few days. There just hasn't been any new news. The issue is still there and they're still working on it apparently. Really hoping they find a fix soon.
[Verizon Samsung Galaxy S III] DreamFX:
How do you know they are working on it?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
I've received multiple texts over the last few days assuring me that they're working on it and asking me to attempt to send sms messages to test if they've gotten it working.
[Verizon Samsung Galaxy S III] djdmbrwsk:
Well that's hopeful. Are the texts from a number or from an email address? I received a weird text message the other day about the issue from an email address.
[Verizon Samsung Galaxy S III] djdmbrwsk:
Interesting. I just flashed this GPE based ROM (for the S4) and no texting issue...

http://xdaforums.com/showthread.php?t=2643031

At this point I'm thinking it HAS to be a combination of code that's been in the CM base for some time AND a network change on Verizon's side. That's the only thing that makes any sense to me.
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
It's been from an email. They ask me so send an SMS because they're running a trace. Hopefully they'll get it working soon.
[Verizon Samsung Galaxy S III] Whisk_33:
I just tried flashing this on the S3. (I know I'm desperate). It didn't stick. Luckily I didn't brick anything. I wish there was something for the S3 like this. I'm rooting for Anti to get lucky with the big V.

I was running Hypderdrive with no texting problems at all. Flashed back to CM and it is all messed up.
[Verizon Samsung Galaxy S III] DreamFX:
Thank you for the updates. Much appreciated.
[Verizon Samsung Galaxy S III] EvoNotion:
For the record, I'm a 717 area code person.

Currently I'm in Missouri. A 660 area code. I flashed fresh SlimKat 3. SMS issue is still a problem. Send 1 message, no more.
[Verizon Samsung Galaxy S III] DreamFX:
Yup there is something wrong with the 717 and 570 itself. If you changed your area to 660 you would be back in business. (obviously your not going to do that.)
[Verizon Samsung Galaxy S III] bass0324:
Somehow, still texting after 3 days being on slimkat and had zero issues. Not sure what the issue is but it is weird that I no longer have it and everyone else is
[Verizon Samsung Galaxy S III] tonybahr:
My texts just crapped out again. Too.
[Verizon Samsung Galaxy S III] neolink1:
It's not just happening in PA, I'm in FL and have the same exact issues.. I clean flashed several different CM build, restored a known functioning nandroid and all present the same problem.

It has to be a network issue, with a possible combination of code on the rom itself. This sucks :(
[Verizon Samsung Galaxy S III] twistedillutions:
Im not in the boat the rest of the ppl in this thread are in. But have u ppl tried going to a TW rom or stock. Seems like everyone running a CM rom
[Verizon Samsung Galaxy S III] djdmbrwsk:
Yeah...TouchWiz works. I'm on the S4 and there is a Google Play Edition based ROM that works too. The odd part is old versions of CM that definitely used to work don't anymore. It's like a combo of a network change and a CM bug.
[Verizon Samsung Galaxy S III] twistedillutions:
Ok. By reading this thread its more of a coding signal problem something not playing nice together
[Verizon Samsung Galaxy S III] DreamFX:
Any updates?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
None, I haven't been contacted in a few days. :(
[Verizon Samsung Galaxy S III] pgmr185:
I have tried the proposed solution of going to Google and de-authorizing all of my devices, then re-authorizing them. It made no difference.

Toggling airplane mode every time is extremely inconvenient, but it's at least allowing me to send texts again.
[Verizon Samsung Galaxy S III] djdmbrwsk:
I think at this point, now that it's been narrowed down pretty far, we need to file an official bug report with CM...how you do that I have no clue, lol. But an extensive writeup with all the info found in this thread and the other thread should be part of the bug report.

Does anyone know how/where you would actually submit something like that to CM?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Hey guys, I've got bad news. Verizon left me a message today; they're blaming any third-party OS that we're running. They asked me to revert to the stock OS that came with the phone, and if I have any issues, to contact them. I'm not sure where we go from here.
[Verizon Samsung Galaxy S III] movieman999:
As someone whose been lurking this thread for a little while, this is pretty disappointing, but I appreciate the effort you put into it. Without a VZW rep who actually wants to help and legitimately knows a thing or two, I'm not sure how to pursue this either. I'm seriously considering just saying whatever and continuing the pain in the butt airplane mode trick. I'm on an HTC One in the 717 area.
[Verizon Samsung Galaxy S III] pgmr185:
My contract end date is right around the corner and this might be just the thing that I need to finally make the switch to AT&T. Verizon is gouging me, but I'm putting up with it because they supposedly have "better service". If you take that away, what am I actually paying the extra money for?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Looks like I'm headed to a TW based ROM. Thank you all for being patient and trying.
[Verizon Samsung Galaxy S III] DreamFX:
I was hoping the bad wind would knock the switch in the towers back to the right position. No such luck...
[Verizon Samsung Galaxy S III] pgmr185:
There was some talk over in the developer's thread that the 3/13 update fixed both the MMS and SMS issue. I just tried, and still having the same SMS issue as before.
[Verizon Samsung Galaxy S III] DreamFX:
Thanks for trying.
[Verizon Samsung Galaxy S III] theraptscallion:
Add the 276 area code (SW Virginia) to the list. A buddy with an S3 cannot send more than one sms without airplane mode, nor can I. Going back to TW fixes it. Has anyone tried going back to before whispersync was added to the codebase (I think it was added in CM10.2 and backported to the latest CM10.1 update)? That's the only thing I can think of that might cause a refusal from verizon, since it is embedded in the rom, rather than the messaging software.
[Verizon Samsung Galaxy S III] DreamFX:
I have
[Verizon Samsung Galaxy S III] Supercutetom:
Add the 757 area code to this as well. Southeast Virginia here and I can't use SMS just like the rest of you. TouchWiz here I reluctantly come.... :(

Edit: I just wanna throw it out there that I've tried a couple different CM ROMs. All the way back to android 4.1. I've tried carbon, slim bean, Slimkat, Paranoid. Nothing but TouchWiz works... SMS sends once and then never again. Bleh
[Verizon Samsung Galaxy S III] Whisk_33:
I was using 10.2 for almost a year without any modifications when the 1SMS issue arose for me. So It wasn't the result of an "new" updates/code on the Rom end of things.

Mastamoon was asking for a logcat of the issue in his thread. I'm not on CM atm. Last I checked he asked if I ever tired re-registering Whisperpush. I can't give him any information since I can't run through the hoops right now.

You can check the thread out here if you guys feel want to give him the info. (I think it is out best shot currently )

http://xdaforums.com/showthread.php?p=51059306
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Just finished up my restore on my reluctantly-installed TW rom. Texting is now 100% functional. This sucks.
[Verizon Samsung Galaxy S III] lopedog:
Same here. I installed an stock backup I had and everything works fine. Except now it keeps trying to install the update. Which one did you install?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
I'm running build 22 of AllianceROM.
[Verizon Samsung Galaxy S III] lopedog:
Kk. Thanks I'm gonna check it out
[Verizon Samsung Galaxy S III] Beavenour:
Bug report with CM?

Has anyone put in a bug report with CM yet? Even if it's an issue on Verizon's end someone at CM has to "know a guy who knows a guy" at Verizon who can get better support than the average Joe Blow like me.

Running Carbon ROM in the 717 area code BTW. I'm just glad I use Hangouts for most of my TXTing.
[Verizon Samsung Galaxy S III] esjames:
The 3/14 nightly seems work work ok, I am able to send out mms and sms like normal. I had to odin back to stock and then come back to CM. For some reason coming from the M3 build to the 3/14 nightly broke it, so thats why i tried the odin way. Seems like some remnants was hanging around that din't want to wipe clean.
[Verizon Samsung Galaxy S III] DreamFX:
Maybe I'm missing something here but you never posted in this thread. What area code are you in?
[Verizon Samsung Galaxy S III] esjames:
757
[Verizon Samsung Galaxy S III] DreamFX:
Yea that's Virginia. Anyone from central pa wanna try? I'm sick of flashing back to cm and losing my texting.
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
If someone could do that for us that would be fantastic, I really don't want to lose my texting again, as much as I can't stand TW.
[Verizon Samsung Galaxy S III] DreamFX:
Just tried doesn't work for central pa still

---------- Post added at 10:28 PM ---------- Previous post was at 09:46 PM ----------

Flashed latest CM. First text only goes through still. Strange thing is I sent like 15 texts they all failed in CM. I immediately restored a TW rom and then all the texts Like 10 mins later went through. So Verizon is def getting the texts on their end their just refusing to allow texts to go through from a non touchwiz rom. Pisses me off!
[Verizon Samsung Galaxy S III] Supercutetom:
Hey guys! Head on over to Mastamoon's CM11 thread. It appears as though a fix has been found
[Verizon Samsung Galaxy S III] gt43aw:
Just an nvrestore (so long as you've done an nvbackup before)? Nice.... I'll probably hold off a few weeks. I've done enough flashing this month :). Hope it works for everyone.
[Verizon Samsung Galaxy S III] DreamFX:
I have been doing extensive testing to try and figure out why us folks in central pa lost texting on aosp roms on 2/20. I downloaded an app called android system info. I launched it on TW(where texting always works) and CM(where texting doesn't), Went to telephony tab and found something rather interesting. The network operator name for TW rom is Verizon Wireless and for CM it's Roaming Indicator Is Off. If you change the ERI file or use an xposed module to removing this from the notification area which it does but never does it change the hardcoded network operator name.

I am thinking for some reason on Central PA towers that they are enforcing the Network Operator name to be correct or it won't allow texts to go through. The reason I know Verizon is actually getting the texts I send because I sent like 15 in a row they all in CM act like they didn't send. I immediately restored back to TW and I received all 15. Something in the CM code (why only for Central PA) which seems like its the network operator or some other similar setting needs to be changed to work.
[Verizon Samsung Galaxy S III] S52Stu:
su reboot nvrestore fixed my issue. Thank god no more TW
[Verizon Samsung Galaxy S III] cooldman224:
Can you elaborate on this? How did nvrestore fix the issue and what you did?
[Verizon Samsung Galaxy S III] S52Stu:
It doesn't work. It fixes the issue for one boot. After you nvrestore and install a ROM (for me it was slimkat) you can send texts until you reboot the phone. Then it is back to its standard 1 text.
[Verizon Samsung Galaxy S III] DreamFX:
Figures
[Verizon Samsung Galaxy S III] Supercutetom:
Does anyone know where else people are looking into this issue? It is not just our phones having the problem
[Verizon Samsung Galaxy S III] theraptscallion:
I didn't have a valid nvbackup (verizon replaced my phone when the gps died after 8 months) but was able to fix the problem by going back to stock and reprovisioning using *2767*3855# I then flashed back to CM11 and I've gone through about 36 hours and multiple reboots and the problem seems to be fixed.
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
We're you having the one SMS only issue and then toggle airplane mode or reboot to send another? I may try it but I just want to make sure we're having the same problem.
[Verizon Samsung Galaxy S III] DreamFX:
Didn't work for me
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Gosh darn. I'm really anxious for a fix. I cannot express in words my deep hatred for TouchWiz.
[Verizon Samsung Galaxy S III] Supercutetom:
I really don't see this getting fixed unless it draws the attention of some higher up developers... :(
[Verizon Samsung Galaxy S III] S52Stu:
Can you elaborate cause all the number does is say call cannot be completed
[Verizon Samsung Galaxy S III] theraptscallion:
By stock I mean straight touch wiz and I think you have to be on Ics. I used Odin and the root66.tar file. Pm me if you have more questions.
[Verizon Samsung Galaxy S III] yooeee:
Could you detail everything here? If this works then many people would benefit
[Verizon Samsung Galaxy S III] efaden:
I agree... can you provide a few more details? I'd like to do it next week and just want to make sure I do exactly what you did.
[Verizon Samsung Galaxy S III] Whisk_33:
It is important for you to have down an Nvbackup at some point if you have an older model (http://xdaforums.com/showthread.php?t=1852255 or at least do a manual nvbackup just in case[/URL])

This is what I did to fix the issue.

use Odin back to a stock w/root

Download CWM and Terminal Emulator

In Terminal type

su

reboot nvrestore

(my phone wouldnt reboot after the nvrestore so i had to flash a new ROM straight from CWM)

I flashed (20140315) CM official nightly

and texting was back.

Beware of what you are doing if you aren't familiar with it. Again, this is what worked for me.
[Verizon Samsung Galaxy S III] efaden:
The nvbackup link didn't work. What if I don't have an nvbackup already?... Can I make one now?
[Verizon Samsung Galaxy S III] theraptscallion:
Here is the foolproof step-by-step

1. Nandroid!

2. Follow the post two above this one for how to odin back to stock ICS touchwiz (ALWAYS FLASH IN PDA!!!!!!!!!!!!)

3. Once your phone has booted, skip all the signups, logins, and whatever until you can get to the homescreen

4. Open the dialer and enter *2767*3855# complete with all asterisks and pound signs

5. Open the command prompt and type su then reboot nvbackup (this will give you a new nvbackup just in case you have this issue again and don't want the hassle of wiping EVERYTHING)

6. Reinstall CWM using odin, rom manager, the all-in one java, or any other way that suits your fancy

7. Install the latest nightly for an absolutely clean & fresh CM installation OR restore your nandroid backup

Special Notes: DO NOT LET YOUR PHONE DOWNLOAD ANY SOFTWARE UPDATES WHILE ON STOCK! Using Odin will wipe your internal SD card, so back that up if you want anything on it. Also, using odin will downgrade your modem to the one that shipped with the phone, just flash the latest modem and you'll be up to scratch.
[Verizon Samsung Galaxy S III] efaden:
Thanks.
[Verizon Samsung Galaxy S III] jhanford:
OMG, so much junk to wade through in order to get to the home screen. It's been about a year since I've been on TW and I can honestly say I haven't missed it (except maybe the camera).

Going through this now as I haven't been able to update CM 11 since 3/13. Will provide feedback if it all works.

EDIT: Success! Now on 3/21 nightly and able to send SMS at last!

FYI: I was testing with an SMS receiving number so I didn't bombard people with texts. The number I used is (201) 345-7341 which is also accessible from a browser at: http://americas.clickatell.com/products/sms-gateway-cmnext/test-sms-gateway/
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
I have a few questions before I try this method.

1. Do I have to have a previously made nvbackup? I haven't made one in the past, but I'm assuming that's why you flash back to stock to make one.

2. Does it have to be a CM ROM? Before my texting died I had been on Carbon and I miss it.

3. I just flash the new modem zip file to upgrade it, correct?

4. I've read in some places that doing the nvrestore causes bootloops. If that happens, should I just boot into CWM and flash my new ROM?
[Verizon Samsung Galaxy S III] xyrcncp:
I haven't done this yet as I'm at work but also victim of this texting issue.

I'm assuming that between step 5 and 6, you'd just log in to your Google account as normal right?