yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] katzer1:
Short answer: I got it to work. Skip to the end of the post if you want to just get the link...

Slightly longer:

Device: Samsung S3, US Verizon, SCH-I535

OS: d2vzw , CM 10.2.1 - last known stable version

Carrier: O2 in the Czech Republic

Prior to installing CM, I had it with ancient Android 4.1.2 (I did not do the OTA update). It was slow, full of bloatware etc.

Symptoms:

I could receive SMS messages but not send SMS.

I never saw "full reception" on the antenna icon on the status bar.

I had data when not on wifi - but it was slow.

Steps taken that did not make a difference:

Fiddling around with *#*#4636#*#* and trying everything written here: http://wiki.cyanogen.../w/SMSC_Updates

Voice+ was not the culprit either. I even under root deleted the apk, rebooted - same deal

Fiddling with the carrier mobile networks did not help either

This worked:

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

I hope it helps.

Best regards and drive safely,

Erez
[Verizon Samsung Galaxy S III] capt730:
If you flash the MB1 AIO, it will solve messaging problems on AOSP. I didn't have messaging problems on TW based roms using MF1 or ML1 modems.
[Verizon Samsung Galaxy S III] Whisk_33:
There is a thanks button at the bottom of the OP. It's linked directly to my self esteem. ;)

Back when we were still looking for a fix this was a temporary workaround. I would switch it to CDMA only and I could SMS for a while. It would eventually (<1day) revert back to not sending SMS and I would then have to reboot)

The best fix is just to stay on the MB1 radio.

If the links are dead, I apologize. Find a new one and I'll update the OP. So for any outdated info.

The OP is still the best way to address the issue.
[Verizon Samsung Galaxy S III] eksoccer99:
Currently have aosp rom installed. So just flash the recommend file/firmware? Or do I need to be on a TW rom first? Will I lose root and/or custom recovery?
[Verizon Samsung Galaxy S III] capt730:
You can just flash the MB1 aio in recovery. It doesn't touch your recovery or mess with root. I flashed on TW rom, tested and then flashed aosp and haven't looked back. You could always try flashing the MB1 while on aosp and if it works, then nothing else for you to do.
[Verizon Samsung Galaxy S III] lopedog:
Did the fix last night. Running like a champ!
[Verizon Samsung Galaxy S III] Corbitt74:
HELP!!!!!!!

PLEASE HELP!!!!

Ok tried the download to MB1 from my SD card, cause I am having the same issue. I'm running Carbon Rom 4.4 KK, with no problems except the

sms issue.

Flashed MB1 and no my phone wont connect at all except to Wifi. Re downloaded VRCUCML1 cause that's what I had before, Same thing no connection!

Down loaded both from SD card

Fyi I'm new but learning. Thanks
[Verizon Samsung Galaxy S III] chinaskyline lily:
Bulk sms business

Dear partner,

Chinaskyline are*Looking for gateway holder for bulk sms business .

Huge live traffic available.

SMS gateway wiil offer in lowest price all time.

Technical supports for free forever in sms business.

Mobile/Whatsapp+ 8615981841633

Skypelive:81d22c5c72247245

email:sale3xs@chinaskyline.net
[Verizon Samsung Galaxy S III] bass0324:
I installed slimkat weekly 3.4 last night (clean flash) from MOAR ROM. So far so good today, still using kernel with slim. All texts have gone through first try. 570 number too and I too had texting issues but I noticed the issues after flashing a unified build. I will continue texting tonight and let everyone know if it is still working tomorrow. Last time I clean flashed AOSP I had the issues come back after a few hours.
[Verizon Samsung Galaxy S III] DreamFX:
Our issue is different. We could flash any aosp ROM ever built from the beginning of time and we still don't have texting. It's a Verizon issue.
[Verizon Samsung Galaxy S III] bass0324:
Yes I know, I had that issue, in order to get one single text to go through you would need to toggle airplane mode or reboot. I switch to TW because of that very issue and couldn't stand the interface so I decided to try the new slim with the new notifications (which is pretty cool BTW) and deal with the one text per wireless connection and to my surprise, it is still working. I also believe slim isn't using unified builds right now too, but not sure about that.
[Verizon Samsung Galaxy S III] capt730:
I didn't have messaging issues before the middle of February when I would bounce around on aosp roms. The stability of TW and some of the features of stock were why clean rom and bonestock were my main roms. That and I was having issues with some of my music not being recognized on aosp roms.
[Verizon Samsung Galaxy S III] S52Stu:
Issue still is not resolved for me in 717 with slimkats newest weekly release.
[Verizon Samsung Galaxy S III] bass0324:
Just curious, did you by chance come from TW or another aosp ROM?
[Verizon Samsung Galaxy S III] S52Stu:
I have been having this issue will all aosp Roms since I flashed the d2lte PA ROM around the 20th of February. This time I did a clean install but was previously on a TW ROM.
[Verizon Samsung Galaxy S III] bass0324:
Yea that was the same time I started having issues. Not sure why but mine seems to be working OK, at least my phone is telling me all my texts going through whereas before they always failed and I would get a notification. Didn't do anything out of the norm to make that happen
[Verizon Samsung Galaxy S III] S52Stu:
Are you in/on LTE?
[Verizon Samsung Galaxy S III] bass0324:
Yup, but preferred network plan is LTE/CDMA/EvDo instead of global
[Verizon Samsung Galaxy S III] S52Stu:
Just tried setting it to that. Still can only send the first text. Then nothing. Shrug thanks for the ideas.
[Verizon Samsung Galaxy S III] bass0324:
Also switched to art, worth a shot I guess
[Verizon Samsung Galaxy S III] S52Stu:
Oddly enough I sent two texts when I switched to art. Then nothing again.
[Verizon Samsung Galaxy S III] bass0324:
Weird, not sure then, I'm still texting with no issues, not sure how that works though
[Verizon Samsung Galaxy S III] DreamFX:
Art has nothing to do with it. Verizon lte is the cause. But I don't know of a fix. I'm researching every angle though. I will update on this thread on any new developments.
[Verizon Samsung Galaxy S III] S52Stu:
Verizon LTE may be the only issue but he is in 570 and texting fine on asop when he described our exact issue before? I hear what your saying, but saying it is IMPOSSIBLE that it is a setting on our phone for a certain area (seeing as I work for a major ISP and know that settings are different in areas across the country) is just ludacris. I believe tests are always worth a shot. I mean no insult.
[Verizon Samsung Galaxy S III] bass0324:
Thank you dex, I am just reporting what i found and am currently experiencing, I spent all of today texting on the latest slimrom without toggling airplane mode and with LTE enabled. I am not sure what it is that is causing me to be able to do so but if there is anything I could get to help you guys out I will gladly try to do so. If I lose texting abilities again at all I will update but 1 day down, hopefully many more to go with no issues.
[Verizon Samsung Galaxy S III] EvoNotion:
I'm from 717 as well and I was having thd same problem. Currently however I am traveling to Missouri and when we get there ill flash back to Slim and check and see if the issue followed
[Verizon Samsung Galaxy S III] DreamFX:
Tests are worth a shot if you have reason to believe it may work. That's like mixing water and sand in a bowl and if you keep trying it will eventually turn into a wedding cake. It's impossible. No setting just magically changed for everyone in central pa. I have tried ALL aosp roms from the beginning for my phone even ones that use to work. Before ART was even around and texting no longer works in aosp. I also odined back to stock which would overright your magical setting. Working for an ISP is a whole another ball game than working for a major cell phone company. Besides any one ever call the big C and your light years more knowledgeable than the person who answers? Let's work together for real solutions not amateur ones that are IMPOSSIBLE. Also I don't have an S3.I have a note 2. People have reported this issue with all makes and models.
[Verizon Samsung Galaxy S III] S52Stu:
I'm not going to make a spat over this. But did I say I was tech support answering phones? Your right insulting people isn't working together I thought trying possibilities was.
[Verizon Samsung Galaxy S III] Whisk_33:
Attempt At a Fix

So I saw this post

Can someone still running CM try this and report back if it works? I truned into a coward and moved to a TW rom. Looking forward to hear back from you guys!
[Verizon Samsung Galaxy S III] DreamFX:
Can tell this won't work. I don't even sign into Google and can't send texts after the first one.
[Verizon Samsung Galaxy S III] Whisk_33:
It isn't clear if you have even tried the suggestion or if you are just adding negative comments. Please clarify.
[Verizon Samsung Galaxy S III] DreamFX:
By no means was it meant to be negative. But to eliminate the possibility of it being a Google issue when I flash a aosp fresh rom I don't even sign into google. I boot up the aosp rom and then skip the setup wizards and go right to texting.

With that said though I am going to try your suggestions just for giggles just to see what happens. I'll let you know if it works.
[Verizon Samsung Galaxy S III] thejudgement223:
Didn't work for me
[Verizon Samsung Galaxy S III] esjames:
Just so you know, I only shared my results as what worked for me, my situation was i could text to my hearts content on any Touchwiz roms. When i installed any kitkat rom, my texting service dropped off into the deep end. I could send out only 1 text, maybe 2 if i got lucky. It didn't matter if i was signed into google or not as I got the same results if i was signed in or i just skipped installing GAPPS completely. When i cleared out all of my registered devices my text service started working again. Please note that my galaxy s 3 was in my devices about 15 times. I believe something got borked on the server thinking my phone was not really there.
[Verizon Samsung Galaxy S III] DreamFX:
Same symptoms for me as well....

Removed all devices

Wiped it RAW

Flashed latest CM

Send 1 text, the rest fail...until reboot, turn airplane mode on/off, or change to cdma

Thanks for your solution. As I'm still sticking with this is a Verzion LTE issue for central PA and some other areas.
[Verizon Samsung Galaxy S III] esjames:
Yea I read that certain area codes in PA is having issues. I don't live in PA. Best of luck to you folks out there. :good:
[Verizon Samsung Galaxy S III] Whisk_33:
Thanks for checking Dream. I saw it as a possibility so I figured I would post it.

I am running Hyperdrive right now which is a TW based rom. Texts all work just like they did before February 20th. If I flash back to CM (10.2 or 11) it goes back to fail.

I will keep checking for answers, but so far I haven't found anything/anyone that has an idea on how this will get fixed.
[Verizon Samsung Galaxy S III] DreamFX:
Welcome. Keep us updated and I will as well as I will try anything at this point.
[Verizon Samsung Galaxy S III] lopedog:
I'm having same issues with a757 area code
[Verizon Samsung Galaxy S III] Whisk_33:
and so it shall be named: 1SMS

So I have updated the OP to include all the information I have to date. Lopedog you are the only one outside of the 570/717 area code I have seen that has reported this issue. Everyone else is with the Central to NorthEastern Pa region.

Just to confirm. You can send 1SMS and then all future SMS fail. You can receive them just fine. You can send and receive MMS just fine. call just fine. etc. Just the outbound 1SMS.

I vote we call this the 1SMS issue.

You have to name it if you expect to catch it...
[Verizon Samsung Galaxy S III] esjames:
Me and my wife are in the 757 area code, only I was affected by the sms fail. My wife runs the CM11-M2 build on TORO and has been running flawless. I started having this issue on sunday moring (3/9) and i was running the 3/1 nightly. I did what I posted a while back while switching to the CM11-M3 build. I guess I just got lucky. :cowboy:

Side note - we are on Verizon.
[Verizon Samsung Galaxy S III] gt43aw:
I have 757 area code and in socal and have this exact issue. 1 text can be sent then need to toggle airplane mode. I'm on cm11. There are other people in socal having this issue as well.
[Verizon Samsung Galaxy S III] Whisk_33:
So you and your wife had the exact same setup, but only your phone had a problem? That doesn't make any sense. You deleted all your authorized devices and that fixed everything for yours? Two other people have tried it here to no avail. No sense makes of this.

It doesn't seem to matter where YOU are, but where your number is from. There was a user who had a 570 (pa) number while living in NJ who had the problem. He moved his number to a NJ area code and the problem went away. So if SoCal is now home for you try changing your area code. and report back!
[Verizon Samsung Galaxy S III] esjames:
I am also curious if everyone having this issue is on the D2LTE builds:confused:
[Verizon Samsung Galaxy S III] DreamFX:
I've had my phone number for like ten years I really don't want to change it. I'll give it another week then I'll probably change mine.
[Verizon Samsung Galaxy S III] esjames:
No we didn't have the same setup, we are both running different devices just running CM11.

-edit-

We also have different accounts, Gmail & GAPPS. I am just trying to give as much info as possible.
[Verizon Samsung Galaxy S III] DreamFX:
I have a note 2. Tried all aosp roms even ones that use to work.
[Verizon Samsung Galaxy S III] Whisk_33:
No. I was running a version of 10.2 which I last flashed in November or December of last year. It was before the combined builds. So... yeah.
[Verizon Samsung Galaxy S III] lopedog:
Ya send 1sms fine then rest fail. Couldn't send mms. Could receive sms and mms fine no problems with calls. I'm on Verizon.

---------- Post added at 07:45 PM ---------- Previous post was at 07:34 PM ----------

I was running carbon 3-10 d2vzw build.
[Verizon Samsung Galaxy S III] Whisk_33:
In my 1SMS issue. I

CAN

send MMS fine. I would end up taking a picture and sending that to my wife instead of toggling airplane mode. Maybe your issue is different is you are unable to send MMS.
[Verizon Samsung Galaxy S III] lopedog:
Maybe. IVerizon tried to help troubleshoot it but again no fix. I restored an old stock back up I had and everything worked
[Verizon Samsung Galaxy S III] Stealth111:
I am running this build: http://mastamoon.truelinux.net/ROMs...cm-11-20140310-UNOFFICIAL-mastamoon-d2lte.zip

and have EXACTLY 0 (ZERO) text mms/sms issues at ALL!

Hope that helps!
[Verizon Samsung Galaxy S III] gt43aw:
Did u have problems before and mastamoon build fixed the issue?

Also, all cm officials are having the problem back to 10.2.1, which was pre lte merge builds. Could be further but i stoped testing.
[Verizon Samsung Galaxy S III] Whisk_33:
Looks like you guys still on CM need to try tonights nightly and report back. Maybe this is the fix we are awaiting.:D
[Verizon Samsung Galaxy S III] DreamFX:
Whisk this is a MMS fix not sms :(
[Verizon Samsung Galaxy S III] DreamFX:
Confirmation from a fellow XDA member that has been testing with level 2 Verizon tech support that this is a Verizon issue. They refuse to fix it and blame "custom roms"

He was texting them back and forth and they can see he was attempting to send sms and could see the failures on their end. Below is the server error Verizon is getting when he tried to send:

403 Forbidden

The server understood the request, but is refusing to fulfill it.

They closed his ticket and said they won't support "custom roms"

:( :( :(
[Verizon Samsung Galaxy S III] DreamFX:
Some of the VA ppl are saying it's been fixed anyone from central pa care to try today?
[Verizon Samsung Galaxy S III] azron34:
I just tried sending and SMS from Pittsburgh - and it worked, but I have only had this problem on and off.
[Verizon Samsung Galaxy S III] Whisk_33:
Ok I have some good news. I devoted the day to working on this and I just sent out 5 sms over a span of 7 minutes. I did a bunch of things though and so there are a bunch of variables and PIT FALLs. But ultimately this is what I did.

I used Odin back to a stock

I the did an nvrestore (you should only do this if you have done an nvbackup at some point)

I flashed todays (20140315) CM official nightly (no gapps)

My texts are working at the moment. (Its only been a couple minutes so who knows if it sticks, Also my phone wouldnt reboot after the nvrestore so i had to flash a new ROm straight from CWM)

I would say try the night and see if it is working for you dream. if not... you may have to try more lethal force.
[Verizon Samsung Galaxy S III] DreamFX:
Remember I have a note 2. I don't know what a NV backup even is. I don't think my phone has this. I'm gonna Odin back again and try flashing CM after flashing twrp and stuff again. Will post back. Your in Scranton whisk?
[Verizon Samsung Galaxy S III] Whisk_33:
correct on the location.

Sorry I couldn't be more specific. If you search nvbackup and mvrestore I'm sure you can find how to back them up or restore it. I certainly am not an authority on the issue but I think phones are supposed to have that information coded into them. The gs3 was having problems because the first batches didn't have it hard coded correctly and people were losing their imei and such so it was wise to do the backup manually.

Long story short. I believe restoring that old back up is what did it for me. I'll report back if it doesn't stick or any other changes. Good luck.
[Verizon Samsung Galaxy S III] S52Stu:
Can you NVrestore another persons nvbackup? I only ask because I don't have one and I have a feeling if I backup now it will only backup the same issue.
[Verizon Samsung Galaxy S III] BadUsername:
No you can't, you'll restore their imei with it.

If you backup now it won't fix anything, you need your good efs information from before the problem occurred.
[Verizon Samsung Galaxy S III] Whisk_33:
[MENTION=5181150]BadUsername[/MENTION]

Correct me if I am wrong, but He could manually back up what we has currently. If he tries an nvrestore and restore nothing he could then manually restore the manual backup?

I don't understand the process much at all so I am definitely asking questions not stating answers.

I did this to fix the 1sms issue for me. I'm having some trouble with the phone getting stuck rebooting and rebooting every other time I lock the screen, but the sms issue is gone. This constant reboot/getting stuck during rebooting seems like it isn't a very good fix..

I just say this in another thread related to this issue
[Verizon Samsung Galaxy S III] BadUsername:
A manual restore with qpst won't fix other issues related to roaming and eri data if a faulty backup is restored.

A manual backup with qpst would definitely be sufficient, but I wouldn't use that unless it's a last resort. If he did back up what he has now and restores it then nothing should go wrong, but I would bet it wouldn't fix anything.
[Verizon Samsung Galaxy S III] S52Stu:
su reboot nvrestore fixed my issue. Thank god no more TW.
[Verizon Samsung Galaxy S III] BadUsername:
Did you have a prior backup? Or did you backup your efs after the problem occurred?
[Verizon Samsung Galaxy S III] S52Stu:
Standby.. I backed up using synergy in case I would need it and just did the nv restore. But after sending a bunch of texts I now am not able to again.

---------- Post added at 05:42 PM ---------- Previous post was at 04:56 PM ----------

Back to texting again. But we will see I'll keep you posted
[Verizon Samsung Galaxy S III] mobilebatty:
Problem also in Central VA

I have spent several days looking into the issue I was having with Verizon LTE and my CM10.2.1 but luckily have found others had the exact same issue.

This started in 804 area code early last week. only fix is toggle radio on/off.

Also occurs randomly on T mobile with CM10.2.0

Verizons "Tech" support just wants to ship out new phone... but obviously its an issue within CM directly.
[Verizon Samsung Galaxy S III] S52Stu:
Didn't stay fixed
[Verizon Samsung Galaxy S III] Whisk_33:
That is odd. The sms fix worked and stuck on mine. I keep getting stuck in a boot loop fail though. If I touch the power button instead of the screen locking like it should, the phone starts rebooting and frequently gets stuck there. Now I wish the phone would quit rebooting like it is, but my texts ARE working...
[Verizon Samsung Galaxy S III] S52Stu:
Maybe odin? And reinstall ROM. It didn't stick for me. Maybe my backup is corrupt as well.

---------- Post added at 08:09 PM ---------- Previous post was at 07:59 PM ----------

Just out of curiosity did you use terminal emulator? Just

Su

Reboot nvrestore

?
[Verizon Samsung Galaxy S III] Whisk_33:
I odin'd back to a stock TW rom. download Terminal Emulator and then did the su reboot nvrestore. During the reboot it just hung on the Samsung Galaxy S III screen for 10 minutes. I pulled the battery and tried to reboot to no avail (it just got stuck on the same screen). I flashed the stock rom again. booted up. Tried texting (it worked). grabbed CWM, booting into recovery and flashed CM11 nightly from yesterday. It took a couple tries to boot up. (the same problem I'm having now) but it boot up. and I haven't lost texting capabilities yet. Knock on wood.
[Verizon Samsung Galaxy S III] S52Stu:
That is pretty much my same process. But not staying letting me send. Hope it works for you.
[Verizon Samsung Galaxy S III] letskillbrad:
I'm having similar issues in the Frederick, MD region. Area code 301. Started yesterday, and I just assumed it had something to do with our mid March snow. Running CM 10.2.1 with no issues prior. Also worth noting, in front of my computer my phone used to get at least 3/4 bars of signal, and then recently (past week) has been getting maybe 1/2 bars.
[Verizon Samsung Galaxy S III] theraptscallion:
I odined back to stock 4.0 (root66) and downgraded my modem to match, reprovisioned the service since the NVrestore just caused a bootloop for me, and restored my nandroid from CM11 and updated my modem. Texting has been working fine for over 24 hours with multiple texts sent to multiple people. PITA fix, but at least it seems to have worked.

To reprovision on stock, open the dialer and enter *2767*3855#
[Verizon Samsung Galaxy S III] letskillbrad:
I switched to CDMA/EvDo using just the regular network settings menu, and SMS was working on 3G, so I opened up LTE and have been texting fine ever since. Perhaps they fixed whatever was going on?
[Verizon Samsung Galaxy S III] EatonZ:
Does anyone here get the error code -1 when sending an SMS? That's what I get. It tries to send it for like a minute and fails with -1.
[Verizon Samsung Galaxy S III] Whisk_33:
Your previous description of symptoms does not match what others (including myself) had been experiencing.

The fix that I have used which has fixed the issue for me. What I did:

Install samsung drivers and unzip the odin executable

boot phone into download mode (hold home, volume down, and power)

load root66.tar in the PDA section

press start

Let it boot up.

Install terminal emulator and CWM.

into Terminal Emulator Input "

Su

reboot nvrestore

It got stuck during the reboot process for me. so I pulled the battery

booted to recovery

wiped caches/factory reset everything

flashed CM11

Everything worked.

DO NOT GO DOWN THIS ROUTE IF YOU ARE UNFAMILIAR WITH THE NVRESTORE PROCESS. If you never did an nvbackup you could be risking restoring a blank file. This process worked for me, however Dex95 tried this and it didn't stick between reboots.

Lastly I think I broken my power button in the process and I get reboots if I ever touch the button. I am fairly certain that is unrelated, but hey full disclosure.
[Verizon Samsung Galaxy S III] S52Stu:
I have to check my Odin tar. I'm not sure mine is 66
[Verizon Samsung Galaxy S III] Whisk_33:
http://xdaforums.com/showthread.php?t=1762204

May the odds ever be in your favor