yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] S52Stu:
Well - I'm going to try it. Can't hurt anything seeing as I know nvrestore doesn't ruin touchwiz for me. It is taking forever to download, but we will find out. Thank you for the luck thrown my way.
[Verizon Samsung Galaxy S III] S52Stu:
When I did this my phone stopped getting LTE and I was able to send all messages. I didn't notice this though until after flashing SlimKat. I believe that on CM11 most recent nightlies I was texting and sending messages on LTE. I'm going to double check this whole thing, but I'm still curious as to if Whisk ever updated his modem to the ML1 modem.
[Verizon Samsung Galaxy S III] letskillbrad:
The problem resurfaced for me after about 24hrs, and I've seen a few other people on here have their messages work again for a day or two until hitting the 1SMS problem again. I switched over to a TW ROM (AllianceROM), and it seems to be working right now.
[Verizon Samsung Galaxy S III] Whisk_33:
So I haven't touched my modems in a long time. I'm CM11 now and if I look at the Baseband it says I535VRLF2. So I guess I need to update that again... firmware and modem iirc. I can grab them from masta's thread I believe. I should be able to just flash them over top yeah? I damaged my power button during this whole process so I need to get that fixed. If I touch the button I am guaranteed a reboot.

Also, where are you at? Is yours working now or no?

All Touchwiz roms have working SMS.

For the good of the order: Has there been any kind of consensus on what has worked for people here?
[Verizon Samsung Galaxy S III] S52Stu:
I lost my LTE to the point that I didnt have it on TW. I called Verizon and they "sent an updated prl" package to my sim to fix the LTE issue. I guess when that got fixed my texts have been working just fine on Slimkat. Now I'm not long into running the ROM, but I will keep up with you guys to let you know.

FYI do NOT dial *228 on your LTE phone. That is how I lost LTE.
[Verizon Samsung Galaxy S III] Whisk_33:
When I read that you were dialing *228 I thought it would break your LTE, but that was after the fact and I figured it wouldn't have been helpful to mention.

I wonder if verizon sending the "updated prl" has any effect on the issue. Good luck. I'm glad it seems to be working for you.

BTW, I need to get my power button fixed. Anyone know of who fixes it/ where I can send it. PM me if you have any suggestions. Thx.
[Verizon Samsung Galaxy S III] xyrcncp:
This happened to me as well. Actually I went to a VZW store and got a new SIM card yesterday at around 6pm ET, at around 10am today, the problem came back. How long have you been running AllianceROM now?

Do you guys think that somehow Verizon may be targeting non-stock ROMs or rooted devices? I know it sounds "conspiracy theorist" but why just CM/AOSP based ROMs? There's also someone in this thread (http://xdaforums.com/showpost.php?p=51269048&postcount=114 ) who says they have a TW phone stock, only rooted and has the same issues.
[Verizon Samsung Galaxy S III] letskillbrad:
I backed up my CM, did a complete wipe and installed AllianceROM yesterday around 12pm EST. Everything has been hunky dory, aside from some UI issues with Play Music, and I'm getting used to TW again.

And yes, it does sound conspiracy theory-ish, someone in either this thread or another made mention of a different signature being sent with the CM SMS compared to the TW SMS. I didn't do anything to double check this, but if that's the case, it would make sense that perhaps Big Red is the culprit trying to squash AOSP ROMs on their devices. I'm not running out to put on my foil hat yet, though!
[Verizon Samsung Galaxy S III] wolficus:
probably a derpy question...

how are the sms messages being sent. i have browsed other random sms threads (for other devices) but are the sms messages being sent over lte, 1x or a mix of both.

if so... then is there a setting to switch between the two.. a hidden menu in the tw based roms?

possible authentication issue if they are being sent over lte??

currently i am in missouri.., thus no isses with sms at all. also using go sms pro.. not sure if that matters though.
[Verizon Samsung Galaxy S III] xyrcncp:
Never thought I could use this image again :D

My coworker got that "theory" in my head, but of the 5 people I checked with at my job, 3 of them have stock TW with root and 2 have GPE rooted ROMs and they didn't have any issues. I was the only one with a CM-based ROM with the problem.
[Verizon Samsung Galaxy S III] BadUsername:
I wouldn't really call it a different signature, it just works around a different framework setting. Aosp messaging will often break on TouchWiz roms and have the same issues as this, mainly because the framework is different. Only fix for this is using stock TouchWiz messaging.

My guess is something with the newer Aosp build framework is breaking the messaging. If Verizon was responsible for this, they couldn't control message output externally, they'd have to block the framework specifically for each device. There's no way they can tell you're using Aosp messaging over stock messaging through text output on their end. If they were behind it, I'd expect to see a small update that could somehow completely block Aosp framework from operating. Which is basically what the locked bootloader accomplishes anyway.

It's most likely a problem on the developers end breaking it , and it could be specific only to our device. That could pose a problem for a potential fix.
[Verizon Samsung Galaxy S III] Whisk_33:
My expectations are device specific. But it is total speculation and talking about conspiracy theories doesn't help anyone.

[MENTION=5181150]BadUsername[/MENTION]

Did you experience this issue? Did the steps I posted in the OP work for you? Did they stick after a reboot? I did an Nvrestore for my phone, but it felt like I was the first one to stumble upon a fix. and I read mixed messages as it what theraptscallion did will stick after a reboot.

I want to make sure this thread stays beneficial for anyone who has this issue and is looking for answers.

Thanks to everyone who trying/helping at gathering the information.
[Verizon Samsung Galaxy S III] BadUsername:
I don't use aosp, only used TouchWiz. I'm actually still on 4.1.2.

Aosp messaging breaks for me occasionally, so I have to use stock messaging. Easy fix since I don't use Aosp anyway.

NV restore sounds plausible, which makes since that it fixes the issue temporarily, but if it's the problem with the rom the issue would eventually resurface unless the problem is fixed.
[Verizon Samsung Galaxy S III] pagnardc:
I tried everything and I can't get it to stick. I Odin back to stock/unrooted 4.1.2. Odin Rooted, flashed cwm recovery, flashed new ML1 modem, flashed liquidsmooth 4.4.2 rom....the dreaded 1Sms returned. I am not sure what I missed....I was on liquidsmooth for 2 months without a hiccup and now I'm stuck back on TW 4.3. Please help! I really want to return to 4.4.2. Thanks
[Verizon Samsung Galaxy S III] S52Stu:
Still texting. Still no issues. Been running slimkat.. Nvrestore seems to have worked.
[Verizon Samsung Galaxy S III] yooeee:
is there a stock s4 touchwiz ICS? i'm having trouble finding it
[Verizon Samsung Galaxy S III] SlimSnoopOS:
S4 shipped with Jellybean 4.2.2
[Verizon Samsung Galaxy S III] yooeee:
yeah thanks, i figured that out. i was looking at the Verizon S3 page (http://xdaforums.com/showthread.php?t=2657822) on this issue and they were reporting that if you go back to stock and do a key code factory reset *2767*3855#, then made a nvbackup, it could fix it. I flashed back to MDK JB and the codes weren't working. Dug some more and found out how to enable hidden menus, but the factory reset / re-provisioning still doesn't work. Anyone have any idea of reprovisioning is possible from out end?
[Verizon Samsung Galaxy S III] Whisk_33:
This is a SG3 forum. I barely know much about the GS3 let alone the SG4.
[Verizon Samsung Galaxy S III] pagnardc:
Anyone know where I can get an ics stock rooted Rom...or should I just Odin back to stock and root after?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Root66. I'm pretty sure this is VRALF2 4.0.3. DO NOT FLASH IF ON VRUCML1 4.3!
[Verizon Samsung Galaxy S III] lv128:
Coming over here from the s4 thread that I've been mistakenly posting in without realizing it.

http://xdaforums.com/showthread.php?p=51393447

To sum up what I've done and hopefully it adds some insight rather than duplicating what's been rehashed:

1. Tried the nvbackup/nvrestore method from a touchwiz rom, did not work

2. Tried flashing a few different modems and kernels, did not work

3. Tried a variety of roms, and anything that is AOSP is not working, only TW varients work for reliable texting

4. Turning the radio down to CDMA 1x in the phone information panel fixes the problem 100% of the time, I don't know why but it seems that the LTE or 3G handoff is banning the handset after sending 1 message. If you stay in LTE or 3G mode, you can send 1 SMS every 2-4 hours after the "ban" has lifted.

5. I've restored chunks of the messaging components from a TB that was created in touchwiz, did not work

6. messing with the SMSC does not work, either in phone info, nor in third party messaging apps

7. this def. isn't an issue with hangouts, voice+, or CM11. The issue occurs on 10.2 and 10.1 as well.

I have verizon calling me every day telling me they have no resolution.

Did I miss anything that someone else tried successfully in the summation?

---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------

I'd agree with this, but why the sudden onset of symptoms on a previously perfectly working handset where no updates were made? I was using 10.2 up until 2/16 at 5pm and the problem just asserted itself with no warning and no updates taken on my end.

So it seems that it could have always been "broken" and verizon has just been accepting malformed sms for a long time and just recently threw the switch to block them? It also seems the sms ban is per handset and per connection to the network, which is why the airplane mode workaround works and the ban auto-expires after a few hours.

This is what I've experienced firsthand.
[Verizon Samsung Galaxy S III] yooeee:
[MENTION=2623455]lv128[/MENTION], I'm coming from the S4 forum and mistakenly took this an S3 forum before, lulz. Anyways did you look the first post about *2767.......? You listed many methods I seen tried failed, but I didn't see that one.
[Verizon Samsung Galaxy S III] lv128:
I did try that but failed to include it in my list since the reprovision only works on the touchwiz rom and not on any AOSP (so far as I can tell) any benefit that may have been gained might very well be erased after flashing a new rom.

But for the sake of completeness I did try it.
[Verizon Samsung Galaxy S III] yooeee:
that sucks... well that search continues for S3 I suppose. I wish I could help more, but I don't have that phone or that problem anymore. contact the original poster in this thread, maybe he/she has some input.
[Verizon Samsung Galaxy S III] Whisk_33:
I've updated the OP. It looks like what I did originally with better instructions. The fix there seems to be working for many people. Try this and let me/us know.

I still haven't had any problems since did the fix on my end.
[Verizon Samsung Galaxy S III] pgmr185:
Just did this last night, and it worked great. Been sending texts all morning.

Unfortunately I decided to press my luck and update to the latest nightly. It seemed to go OK, but when it rebooted it got stuck in a boot loop.

I got everything running again by recovering using the backup I made last night. Not ideal, but definitely the best of a bad situation.
[Verizon Samsung Galaxy S III] net-cat:
Just reporting back about my solution.

Text messages are still sending fine, though I noticed my GPS was out. Flashing back to stock and letting it get a GPS lock fixed the problem. (I added it as a step in the procedure.)
[Verizon Samsung Galaxy S III] barakaspeed:
Here's my recipe that worked... and some observations...

ROM: CM11 d2vzw M3

Modem: ML1

Firmware: VRBMF1

Location: Hershey, PA

Phone: 570-575-XXXX

(attaching catlog first doing a successful SMS and then when it would fail)

I did do a 'reboot nvbackup' back when I first rooted my phone (thankfully), so I did a nandroid backup. Installed 10.0 for kicks and still was affected with the 1SMS issue. I then opened terminal, typed 'su' then Enter. Then I typed 'reboot nvrestore' then Enter. Phone rebooted as expected and boot looped as expected when doing the nvrestore. I went into recovery factory wiped the OS and booted back into 10.0. I was able to send SMS perfectly, until I rebooted, then it returned. So I booted into recovery and applied the AIO VRBMF1 (http://invisiblek.org/sch-i535/aio/I535VRBMF1_firmware.zip), booted back into 10.0, did a 'reboot nvrestore', did a factory restore, then SMS worked again until the next reboot.

So I then applied AIO VRBMB1 (http://invisiblek.org/sch-i535/aio/VRBMB1.aio.zip), did another 'reboot nvrestore', did a factory restore and booted back into 10.0. Now SMS works consistently after each reboot. I then restored my nandroid backup of CM11 from the beginning and SMS continues to work perfectly.

I don't think any of this is particularly new, but it appears VRBMF1 and ML1 are problematic with AOSP for some reason. I would love to know what changed on Verizon's end, as I was using the VRBMF1 firmware for some time prior to when this all started. I also wish I understood more of what nvbackup/nvrestore does at a lower level. Anyways, I am very appreciative to everyone that has carried us this far. Hopefully soon we will get a better explanation and solution.
[Verizon Samsung Galaxy S III] buffal0b1ll:
So I just tested my theory and it worked. I was on MF1, had a good nvbackup from the last time I did post 109 recipe from this thread http://xdaforums.com/showthread.php?t=2658572 , and lost texting after about 12 hours after reprovisioning again yesterday. Followed the steps below and texting is back for now on MF1.

1. Make a nandroid --optional if you already have a nandroid you can use--

2. Run su>reboot nvrestore (this will throw you into bootloop)

3. Boot into recovery

4. Restore your nandroid
[Verizon Samsung Galaxy S III] Whisk_33:
I've been trying to keep up with thread... I keep seeing people posting the steps that they are doing on their phone to resolve their issues... It seems to be clustering the thread some, but it all provides new data.

I haven't seen anything that justifies me updating this threads OP any further. What I have posted there seems to be the most foolproof way to fix this issue. There does seem to be some correlation with the 1SMS issue and the modem, however, there are other individuals that simple do not experience the issue.

If I need to update the OP, please say so in your post. While it may not be necessary to use ODIN, it looks like that will definitely fix the issue and therefore I am going to keep that until I hear more people who have fixed it without needing ODIN.

P.S. The other thread may have more activity in it, but I try to keep the OP updated with the most up-to-date information. Thread merging isn't necessary and there is no need to double post. The 109 post from that thread references the 107 post that I made. The OP here has all that information and more. This was done so that people can easily identify the problem and recognize the solution.

As always, thanks to everyone that is working on this issue.
[Verizon Samsung Galaxy S III] eaglesfan398:
Did you just apply that AIO VRBMB1 in your cwm recovery. Also did you have to boot back into your rom to do a nvrestore and then reboot back into recovery? Also what does booted back into 10.0 mean? What did you factory restore to? A stock rom that you had in a nandroid backup?

Thanks For the Help
[Verizon Samsung Galaxy S III] barakaspeed:
Yes I did apply AIO VRBMB1 in recovery. Yes, after you do a 'reboot nvrestore' you must go back into recovery to either do a factory reset or restore a nandroid backup. Oh, booted back into CM10.0 (this was just me experimenting). Factory restored to factory default (wiped, cache/data etc) I didn't have to interact at all with any stock or TW ROMs. MAJOR NOTE: I did a 'reboot nvbackup' back when I first got the phone. If you didn't you'll need to follow the longer solutions found in this thread. Hope this helps.

BTW: I threw in the towel on this tonight.. I have a Moto X now.. (loving it, but hoping for a reliable bootloader unlock)
[Verizon Samsung Galaxy S III] eaglesfan398:
Did what you do not work now or is it working? Also do i need to unzip that file or just flash as is?
[Verizon Samsung Galaxy S III] eaglesfan398:
So I may have had an solution to this problem. Yesterday I was having problems with texting so I decided to reflash back to the old B1 baseband then I did a "reboot nvrestore" then I restored stock software that came back to the phone tried texting worked perfect. Then after that I wiped data and cache then restored to the stock rom. Then booted into the rom checked texting. Cleared all data. Then after that I booted into recovery (optional: made another empty backup of the stock rom) wiped data, cache, dalvik cache then installed liquid smooth (or rom of your choice) and installed gapps and now my texting is working perfectly. I have been currently running the rom for since 11:00 last night and it is still working. I will post an update later to see if texting goes back out. For people that have trouble sending texts do you usually have like 1 bar and it fails or full bars?

Hope this helps!
[Verizon Samsung Galaxy S III] lowmanb94:
Thanks!

I don't have anything particularly insightful to add, although I can confirm that my experience aligns perfectly with everyone else's on this thread (just found it today).

Seeing as the MF1 firmware (w/ modem) and ML1 modem seem to bork outgoing sms, is the MB1 firmware the next-to-newest? I can't seem to find a list anywhere.

I am also curious as to what exactly has changed. Most intriguing is that the same firmware/modem packages work on TW roms, but not AOSP. That would suggest that the issue is independent of the firmware, which doesn't seem to be true based on the collective experience in this thread. Even more perplexing is that a change on verizon's end caused the issue in the first place, not ongoing AOSP development.

My guess is this: in some way the ROM sends some sort of information with outgoing SMS on the basis of the firmware -- the firmware itself doesn't do anything. Verizon, at some point in the recent past, made some change that blacklisted / fails to process the specific information (or lack thereof) sent by AOSP in accordance with the MF1 / ML1 firmwares.

Thoughts?
[Verizon Samsung Galaxy S III] Travisholt92:
I had a similar issue the other day, i had been running carbon d2lte 3/27 since it was released, my phone got shut off by verizon, I got it turned back on, called verizon because it no longer detected my number or anything, they refreshed my sim, i restarted the phone and was able to have data but not anything else, when i tried to make a call it would just freeze the dialer. switching to CDMA only allowed me to call *611 but still would not detect my phone number, so did a system,data, and cache wipe and reinstalled the rom and it fixed it. Its a CM based rom so i kinda figured it would fit here and thought i would give my solution.
[Verizon Samsung Galaxy S III] mamill66:
Question

Maybe this is a stupid question but, do you think that the developers of let's say Cyanogenmod are aware of these issues? It seems like it's such a small percentage of users that are experiencing these problems.... Only certain area codes on Verizon. If they are not aware, how do you convey issues like these to them?
[Verizon Samsung Galaxy S III] Whisk_33:
your symptoms and solution is not applicable to the 1sms issue. Clean installations of CM and other versions of cm based ROMs do not fix the 1sms issue.

I believe they are. I would suggest making an official bug report on CM. You'll have to be on a non nightly version to report bugs. But the more reports the more likely to get results.

My phone hasn't had an issue since I fixed it. I don't know if this is still happening to people frequently or not.
[Verizon Samsung Galaxy S III] cooldman224:
I found this guide to be best and followed it. Though like this guy I already had these files from when I first unlocked my S3. I am confirming texting on LTE with CM M3. My firmware is that of the 4.0.4 image, I535VRLF2, as well the baseband. I upgraded my firmware to MF1 and modem to ML1 and then lost ability to text. Just FYI for anyone else. A recommendation though is on step 8 to use the EZ-Recovery app instead of manually entering the command because the app enters the same command (I looked at the source if you're interested).
[Verizon Samsung Galaxy S III] lv128:
Verizon replaced my phone

I promised to follow up with new information, and the end result is that Verizon replaced both of my samsung handsets with HTC phones at the upgrade cost without me losing my unlimited data, I did however have to go as high as executive customer care and e-mailing the regional vice president to get that far. Regular tech, NRB, and customer care were just a broken record of "wait until they fix it" and it had already been broken for 2 months, I had enough of their delay tactics.

So the best solution by far is to replace the phone with an HTC M8, unlock the bootloader and although there are no roms available yet for it, I'm content with the less-gross Sense UI that HTC uses over the awfulawfulawful touchwiz.

Not much of a solution, I know....:silly:

All in all, NRB was on top of the problem, but they honestly have no idea what they did server side to cause the SIP 403 error, it was typical tech support, one person does something and doesn't make a lick of documentation, and everyone else scrambles around trying to figure it out.
[Verizon Samsung Galaxy S III] Whisk_33:
It seems a lot of people are having luck my going back to an old old firmware/modem. It's nice to know that you got results, but disappointing that it is happening none the less.

Just to clarify. You hadn't tried the method currently posted in the OP here correct? Since I have done that, I haven't had any issues with the phone. (I did have a button failure but that was hardware and have been fixed). Congrats either way.
[Verizon Samsung Galaxy S III] Anayalata:
So I'm in the Los Angeles area. I used to be on PAC 4.2.2 with no issues.

Flashed PAC KK as soon as it was released with 1 issue that I only recently diagnosed. My data would sporadically go off/on causing my phone to 'refresh' over and over until the data stabilized. During this time I would be unable to send/recieve calls, texts, etc. It would go on for only a minute or so, but it would happen probably every 30 minutes.

I was stuck on the PAC KK March 4 build. Flashing any build after that caused me to lose the ability to send SMS. I would also lose any access to the Verizon APNs. I never the whole Odin method though I did try flashing the LK3 modem with no luck.

Getting desperate I flashed the AOSP Carbon Rom today. Why that one? It's one of the few AOSP Roms that's still putting out dedicated Verizon builds. I downloaded and clean flashed the 4-4-14 build for d2vzw along with the MF1 modem and Ktoonez kernel. Zero issues with sms/mms/data/calls. I've only been running it for about 12 hours, but the instability that was present on PAC is gone.

My only conclusion is that this SMS issue is caused by the unified d2lte builds.

Just passing this along.
[Verizon Samsung Galaxy S III] mamill66:
If I'm reading the OP correctly, is it true that ODIN does not need to be used if there is no nvbackup and a TW nandroid exists?
[Verizon Samsung Galaxy S III] tpearsall:
Net-cat's steps from post 120 resolved the 1sms issue for me. Didn't require a nvrestore. Thanks for working this wacky issue. Todd from Baltimore.