yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] goldsmitht:
Interesting issue: I'm on stock rooted 4.3 (ML1) rooted with SafeRoot but haven't done anything to it.

and i have had issues sending texts the past 2-3 days. at first i will have no issues sending, then BAM! nothing. sitting in same spot as when they go through, looks like i have plenty of bars, all the basic checks work out, have data and signal. I can recieve them, just can't send them.

SO... since i am on touchwiz, stock (other than just rooted but haven't frozen anything) it would seem to me that this is an intermittent VZW issue in the northwest region (I'm in Baltimore)

:confused:
[Verizon Samsung Galaxy S III] buffal0b1ll:
I'm in Baltimore too 443 area code. On 3/18 texts stopped working on Liquid. I tried multiple clean flashes of AOSP ROMs, nandroids, nvrestore, Philz EFS restore, Odin back to stock JB ML1and back to clean AOSP before I resorted to installing Clean ROM 8.1 which works for texting now.

Tonight I'll try Odin to ICS, provision, nvbackup method in this post and see if it works.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I actually just started having this problem on Alliance build 22 today. Yesterday and the previous six months or so I was on SlimKat with no issues even as the "1 sms" issue started to crop up for folks in the Pennsylvania area. As of mid-afternoon yesterday, I had to move to TW to be able to send sms again. Now, not even a day later I am seeing this issue again on TW. I live in No. VA and frequent DC and this was not happening while I was in DC yesterday smh :confused::mad:
[Verizon Samsung Galaxy S III] yooeee:
I'm in Tucson and this problem started around 3/18
[Verizon Samsung Galaxy S III] buffal0b1ll:
You, sir, are a freaking genius. This worked perfectly!

I was just getting used to TouchWiz again, too;)

Would this have worked on CleanROM 8.1 too, or did I really have to go born-again-virgin to get it back on ICS stock.

Also, I updated my modem to ML1 using the modem-only pack. I DIDN'T run the MF1 AIO.

I wonder what would have happened if I ran both: MF1 AIO, and then ML1 modem only,
[Verizon Samsung Galaxy S III] jhanford:
I can only go by my experience yesterday, but:

1. I did not have a previous nvbackup. I did it prior to Odin and restored after Odin

2. I wouldn't think so. Just flash a ROM. Might be worthwhile having a CM available just in case, though

3. I didn't flash new modem

4. I got the Samsung Galaxy S3 screen and it stuck there. Boot into recovery (Vol. Up + Home + Power) and flash a rom
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
But you did get the issue resolved?
[Verizon Samsung Galaxy S III] jhanford:
Sorry, I assumed ;)

Yes, all is working and even updated from 3/21 to 3/22 this morning and SMS is still good.
[Verizon Samsung Galaxy S III] Briden:
This is what worked for me, too. Provisioning while on stock ICS did not.

FWIW, I used TWRP recovery, and ADB to run nvrestore. Mine also soft bricked after the nvrestore.
[Verizon Samsung Galaxy S III] samsgun357:
Man I just randomly starting having this texting issue, Northern VA. Guess I'll have to try as mentioned above.

Watch, as I combine all the juice from my mind...
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Guys I was able to get my SMS back using the nvrestore method. I'll keep you posted if I fails to stick, but it's already survived a reboot.
[Verizon Samsung Galaxy S III] devmage:
For those who would try the `nvrestore`, be aware that it can break both your recovery and your installed rom. I just went through an afternoon of pain after a bad `nvrestore`. ODIN saved the day for me (after Heimdall failed), so you might keep that handy if you're working with this.
[Verizon Samsung Galaxy S III] Briden:
Ugh... was running fine for a ~day. Flashed between CM and Carbon a few times. Finally settled on Carbon. Ran fine through a couple reboots. I hadn't touched the modem so was still on vralf2 from the root66 rom. Decided to flash the ml1 modem. After reboot, SMS issue started again. facepalm
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
I read somewhere that the ml1 modem doesn't work. I haven't had any connectivity issues with my current modem so I'm just gonna stick with it. I'll let you know of it stops working.
[Verizon Samsung Galaxy S III] S52Stu:
I have been running great without updating my modem after odin. I'm wondering just like how Verizon locked the bootloader differently for 4.3 if they also put a patch in the ml1 modem. Or the modem we are all flashing is somehow corrupt. I'm not 100% that its all Verizon blocking it. I think at this point with it showing all over the country they would have said something from the phone calls. OR because custom Roms have issues with too much data and not paying for tethering I believe they would have blocked data not text. It doesn't make any sense to block only text. Just my humble opinion.
[Verizon Samsung Galaxy S III] Anayalata:
Just chiming in...

I had no issues while on PAC 4.2 RC (the last one he released from 4.2)

I flashed KK as soon as it was available and everything was great. The last one I flashed was 3-6-2014 (March 6). If I try to flash any one after that, it gives the same problem everyone else is/was having. I am able to receive but not send SMS. Phone calls, MMS and Data are OK.

I'm running ML1 baseband as well. One thing I noticed was that on the 3-6 build, under Wireless&Networks>More...>Mobile Networks, I'm able to access the APNs. It will list all the Verizon APNs (vzwapp, vzwadmin, etc...). Flashing any build after that and the option becomes grayed out and I lose all ability to send SMS.
[Verizon Samsung Galaxy S III] tech9tcv:
What worked and might work....

I took the advice of flashing back to stock rooted VRALF1 (I had to boot into recovery to wipe data/cache afterwards to get the phone to get past the boot animation) . Used EZ-Unlock (Rootzwiki Adam Outler for d2vzw) to unlock. Installed TWRP (TWRP Manager from market). Restored my phone using the *2xxxx settings. Performed NVBackup. Reflashed LS 3/22 build. Haven't had a hiccup yet. Messaging has persisted over several reboots. Haven't yet had to perform NVRestore. Good luck to you all. I suspect that all you needed to do was flash back to TW and restore phone, but I bricked my phone performing an NVRestore when I have never done the backup. If you are too lazy to do all that, you can just send mms messages all day to your GV # and the person you're trying to send an sms to.

I forgot to add that I had a trouble ticket with Verizon. As soon as I restored phone settings, I got an email from Verizon saying that my ticket was closed.
[Verizon Samsung Galaxy S III] buffal0b1ll:
I used Odin, reprovision on ICS, and restored LS 3/13 nandroid. I then flashed ML1 modem only. Texting worked fine across many reboots. But I noticed that it had stopped working after dirty flashing LS 3/22.

I'm enjoying test driving TW ROMs now. Currently on Alliance ROM which is very nice. I'm having as much fun coming back to TW as I had leaving it a year and a half ago :)

Allows AOSP lockscreen, and xposed GB JB allows setting targets.
[Verizon Samsung Galaxy S III] Briden:
I'm still running CR 8.1... at least until I pick up my new HTC One M8 at 1 today.

Anyone want to buy a used, mint condition S3? :p
[Verizon Samsung Galaxy S III] pagnardc:
Okay... I follow the steps above and everything is working great. I do have one question... I am still on VRLF2. Should I flash the new modem or leave it. I don't want to have to start from scratch again if I don't have to. I guess I'm asking if anyone has flashed the new modem and kept sms working. Thanks
[Verizon Samsung Galaxy S III] S52Stu:
Didn't work for me. It screwed my texting then
[Verizon Samsung Galaxy S III] pagnardc:
Thanks buffal0b1ll. I'll wait to flash until we have more info or I can find someone who has done it and not lost sms.
[Verizon Samsung Galaxy S III] buffal0b1ll:
I flashed ML1 and things were fine for about two days. Then sms was borked again. Going camping in Extended Service area and/or dirty flashing a new LS nightly could be suspect cause(s), but for now all I can say for certain is they are just positive correlations to losing sms again after reprovision on stock fix.
[Verizon Samsung Galaxy S III] helobubba88:
This problem hit me in Maryland while on SlimKat.

Did not provision; just clean flashed Alliance ROM a week ago and haven't had any problems with texting so far.
[Verizon Samsung Galaxy S III] pagnardc:
Thanks buffal0b1ll. I'll wait to flush
[Verizon Samsung Galaxy S III] pagnardc:
Sorry... The above post should say flash.... Not flush...but either way it works. Thanks again. All is still well with me sms.
[Verizon Samsung Galaxy S III] sethdrummer:
Im from the Harrisburg area, some problem, i updated to the newest modem and it fixed it Ml1 hope that helps
[Verizon Samsung Galaxy S III] pagnardc:
Okay, so in response to the comment above.... Is there anyone else out there who is on the ml1 modem on cm 11 or another 4.4.2 rom that still has sms? I have had to reprovision my s3 to get sms back and I'm on the F2 modem. I'm having some reception issues and slow data... Itching to upgrade modem to see if that helps. Any thoughts? I know it has been a problem for some... Just checking of there are others out there. Thanks
[Verizon Samsung Galaxy S III] wolficus:
From what I have been reading some are having the issue return after flashing the ml1 radio.

I was using ml1 but went back to the mf1 firmware... Oddly my reception went way up. *shrug*
[Verizon Samsung Galaxy S III] buffal0b1ll:
Yeah. I've been thinking of starting over and only updating to mf1 aio. I have a theory that this problem arises because ml1 can only update the modem. But what do I know?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You wrote "MF1" twice accidentally. VRBMF1 aio updates 7 partitions. VRUCML1 firmware zip only contains and thus updates the modem, every other partition is left on VRBMF1 or whatever your prior base was.

For me, when I tried the OP's steps, when I was finally back on AOSP with ICS VRALF2 baseband, I could text but after flashing the VRBMF1 aio, I lost sms again.
[Verizon Samsung Galaxy S III] buffal0b1ll:
That's right. I edited my post
[Verizon Samsung Galaxy S III] pagnardc:
I went back to the beginning and ended up on vrlf2 and went ahead and flashed the newer F1 modem and I'm still good with sms... It was a couple days ago and no problem at all. Just FYI I'm on liquidsmooth nightly 3-28. I'm hoping all continues to be well with my sms.
[Verizon Samsung Galaxy S III] Stealth111:
I am on the ML1 modem, CM11 (4.4.2), 03-29 Nightly (the one that was pulled) and my stock messaging (mms and sms) are fine.
[Verizon Samsung Galaxy S III] Desuanian:
There's a lot of stuff here, but I'm hearing/seeing some fixes, but I'm not sure what I need. I'm having this issue on my Verizon S3 running the latest nightly build of Cyanogenmod. It doesn't seem to matter which version of CM that I use, I still have this issue. My phone will send one text, then refuse to stop sending, but I can still receive. I can also send MMS and use my data. Therefore, 1 reboot = 1 text. Super annoying, although the boot time is quick.

From here, what should I do to fix this issue, or do you think I should wait it out until it's fixed? My problem could be hardware, but I'd like to do everything software wise I can before I go ahead and try doing any physical repair.

Also, I'd like to raise a point. Don't you find it a bit odd that a whole bunch of S3 users are suddenly having this problem. From what I've seen it's not just CM users, and I think that's a bit strange. Do you think there was a security hole somewhere? I just think it's super strange that it all happened around the same time for everyone with the issue...

I hope that I can get some sort of help with my problem and can fix it up, but texting isn't the main use of my phone as of right now, so I could live for a bit without it.

EDIT:

It seems that I'm wrong in what I thought, but I'm still looking for fixes. I'm also working on finding my own. Hope we get an official fix soon. This is annoying!
[Verizon Samsung Galaxy S III] buffal0b1ll:
Post 107 and/or 109 is the fix. Good luck.
[Verizon Samsung Galaxy S III] pagnardc:
Well.. I spoke too soon. I was fine after flashing the F1 modem... For 2 days... Now I'm back to having the issue. I tried nvrestore... No luck. I had to flash back to Alliance 4.3 rom. I was doing fine on the really old vrulf2 modem with 4.4.2 except that my data speed was terrible and phone reception wasn't great either. I am dying to get back to 4.4.2. Hopefully someone will figure this whole thing out. I just don't understand why not everyone with an s3 is having this issue... It doesn't make sense.
[Verizon Samsung Galaxy S III] Briden:
So I did pick up the M8 on Tue. I returned it on Sat. Not because the phone isn't great. It is. Love it. I'm just tired of Verizon. So I'm jumping ship.

My AT&T SIMs are coming today. I've got 2 unlocked M8s on order from HTC. Should hopefully be here Fri or early next week.

To Verizon I say AMF!!

In the meantime, I'm back on my GS3 and CleanROM 8.1. It's not easy after sampling the M8 and Sense 6 for a few days. Good luck to everyone on figuring out that SMS issue.
[Verizon Samsung Galaxy S III] esjames:
For what it's worth, the VRBLK3 version works fine for me.

I did some poking around this morning for a few hours and here is what I did and the results.

From VRBLK3 I flashed the MF1 aio, = SMS borked,

""""""""""""""""""""""""""""""""ML1 modem, = SMS borked.

Going back and forth didn't really matter.

Odin back to stock VRBMF1, used Beanstown motochopper (great program btw :) ) Wiped and flashed CM = SMS borked.

Now i'm back on LK3 and probably will stay here for a while as I grown quite fond of our AOSP roms.:)

All tested on the 3/29 nightly build.

Only fallback is the cell reception for the LK3 version less than satisfactory during phone calls, other than that I haven't noticed any data speed difference, not that it really matters to me. Also on a side note, I tried to do an OTA update in this version and said I was on the latest release.
[Verizon Samsung Galaxy S III] buffal0b1ll:
After a week on TW CleanROM and TW Alliance ROM I really wanted to come back to Liquid. Both of those TW ROMs are not very stable on my device. Maybe it's xposed related, maybe it's kernel related (I tried stock, KT747, and LK on both).

SO HERE'S today's story:

I've been screwing around with trying to get texting to work on Liquid all day today.

Repeated the process that worked last time: Move stuff to ext_SD, wipe data and caches, Odin to ICS, reprovision #, Odin TWRP, Flash Philz in TWRP, restore 3/13 LS nandroid....TEXTIING WORKS

Went for MF1 AIO zip instead of ML1 modem only. STILL WORKS

Tried to dirty flash LS 3/28.. BROKE TEXTING and G+ force closes in that nightly;-(

Tried different flashing, playstore, and root explorer placement of alternate messaging apks like someone on G+ suggested. TEXTING STILL BROKEN

Tried flashing MF1 AIO again TEXTING STILL BROKEN

Tried restoring 3/13 LS nandroid again TEXTING STILL BROKEN

Ran su>reboot nvrestore, booted into recovery, and restored 3/13 LS Nandroid again TEXTING FIXED AGAIN

Gonna stop here for today, but it seems like the next time I dirty flash LS nightly, I'll just have to boot it up, confirm that texting is broken again, reboot into recovery, make a nandroid, reboot, su>nvrestore again, recovery restore the new nightly nandroid, and theoretically texting will work again.﻿

---------- Post added at 01:45 PM ---------- Previous post was at 01:40 PM ----------

So the long story short is:

If you fixed texting using instructions in post 109 of this thread, and you made a good nvbackup at that time, you can theoretically fix texting that breaks after a few days or a susequent dirty flash by doing the following.

1. Make a new nandroid and reboot system

2. Terminal emulator>su>reboot nvrestore

3. Boot into recovery and restore your new nandroid
[Verizon Samsung Galaxy S III] samsgun357:
The new cm that dropped today has some added vow APN info. I'm curious to see if this will fix this SMS issue.

Watch, as I combine all the juice from my mind...
[Verizon Samsung Galaxy S III] DreamFX:
Someone please try and let me know how it went.
[Verizon Samsung Galaxy S III] barakaspeed:
didn't work for me.. :( this is so frustrating..
[Verizon Samsung Galaxy S III] DreamFX:
Agreed. Thanks for trying.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Yeah, thanks. The comments in cm gerrit for that commit referred to mms only, but it was definitely worth an optimistic try.
[Verizon Samsung Galaxy S III] barakaspeed:
Would be nice if we could merge these two threads, as I keep bouncing between the two looking for updates. If anyone is interested, this is what fixed it for me (at least for the last couple hours).

http://xdaforums.com/showpost.php?p=51543859&postcount=124
[Verizon Samsung Galaxy S III] buffal0b1ll:
FYI. The hoops I jumped thru yesterday to get texting working were fruitful, but short-lived. Less than 12 hours in, the problem returned. Maybe a positive correlation with pulling battery for battery swap.

---------- Post added at 08:28 AM ---------- Previous post was at 07:57 AM ----------

So I just tested my theory and it worked. I'm was on MF1, have a good nvbackup from the last time I did post 109 recipe, and lost texting after about 12 hours on fix 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] Lorenzo VonMatterhorn:
So essentially, you can skip having to odin back to stock using this method? I am ocd about failsafes so as soon as i got my phone before flashing custom roms i did an nvbackup . i can skip odin and just use this method? thanks in advance sir.:silly:
[Verizon Samsung Galaxy S III] buffal0b1ll:
It might work. I tried the nvbackup I made in December 2012, but it didn't work. But that doesn't mean it won't work for you. I have a feeling that the nvbackup with the LF2 radio in root 66 ICS is what does the trick.

Make sure to nandroid first. When you run reboot nvrestore from terminal emulator just be ready for a bootloop and a battery pull and booting to recovery manually to even be able to get a nandroid restored. And also be ready to Odin root 66 if you have to...to prep for that you'll want to move everything important off of internal SD and wipe cache and data before you go into download mode. Having the TWRP 2.3.7 tar handy is a good idea to, you can flash that from Odin too.

Good luck.
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
Sorry to keep being a bother, but where can I grab that ICS .tar?
[Verizon Samsung Galaxy S III] buffal0b1ll:
The link to the root 66 is in the Odin link in post 107 in this thread
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
Sorry to be so needy, but do any of you guys have the mf1 modem only zip? i have seen talk about it in this thread, but all i can find is the complete firmware package. :confused:

Edit : I have successfully performed the steps in post 109 and now have texting back on Carbon 4/1 nightly. So excited. I just would rather be on the MF1 modem if someone can point me to it.
[Verizon Samsung Galaxy S III] AdMire:
http://invisiblek.org/sch-i535/modems/d2vzw_ML1_modem.zip

Original link from here: http://xdaforums.com/showthread.php?t=1788313
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
Thanks, sir but i am looking for MF1 not ML1 . any ideas?:silly:
[Verizon Samsung Galaxy S III] AdMire:
Ahhh, my bad!
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
......................
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Second link, first post. You'll find it under firmware. There is no "VRBMF1 modem only" zip, it's all or nothing (literally) for the two 4.1.2 firmware zips.
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
sorry for the confusion.
[Verizon Samsung Galaxy S III] DreamFX:
All the folks trying to get aosp texting working on Note 2's and this method didn't work please PM me your phone number I'm going to let VZW know everyone on here who is having issues so I can have some engineers work on this.
[Verizon Samsung Galaxy S III] Whisk_33:
Dream,

I believe you have been to this thread already http://xdaforums.com/showthread.php?t=2657822 have you seen the latest update to the OP. It seems to be working for most people. I try to keep the OP updated with the best/shortest/easiest method. I certainly don't know the details of the modem for the Note2 but this fix has been holding for many peoples. Good luck.
[Verizon Samsung Galaxy S III] DreamFX:
Yes I am subscribed to your topic. Note 2 doesn't have NV restore and backup mount points so your method doesn't work for us. I tried flashing every TW rom available for note 2 and reprovision and then restore a cm nadroid but issue remains :(. I literally have tried everything from the moon and back.
[Verizon Samsung Galaxy S III] Whisk_33:
Does the problem go away once you are in a Touchwiz rom? Or a day one stock rom?
[Verizon Samsung Galaxy S III] DreamFX:
Problem goes away in any TW rom ever made for note 2. Flash aosp or restore aosp it comes right back.
[Verizon Samsung Galaxy S III] Whisk_33:
Yeah, same thing for the GS3. But when we go back to the MB1 modem package and then load up a TW rom everything stays golden. The issues (at least for the GS3) only shows when you are on the MF1 and AOSP roms. I don't even know if the modems and such are the same on the Note2.

Sorry I couldn't help any more. I know little about the GS3 and less about others.
[Verizon Samsung Galaxy S III] DreamFX:
I appreciate any help. I'll keep you posted if I ever figure this out.
[Verizon Samsung Galaxy S III] np726:
Network Extender?

First off, excellent post. Just read through, will try solutions when I get home. However, I've noticed something myself that I haven't seen anyone else mention yet.

I'm running CM 10.1.3-d2vzw and MF1 modem on GS3. When I'm at work, or anywhere else for that matter, I am experiencing the typical 1SMS behavior, having to cycle in/out of airplane mode whenever I want to send an SMS. However, I never experience these issues when I'm at home, where I have a VZ Network Extender...

Not sure why this is the case, but thought it would be worth pointing out...
[Galaxy Note II N7105 Android Development] slysurfer:
Thank you for a new rom. Downloading now, will report back soon. :)
[Galaxy Note II N7105 Android Development] Senyaka:
Just flashed. Very smooth and feature rich. Runs very nicely with agni kernel. Thanks for the hard work. Awesome work.

Sent from a Kaiju killing Jaeger
[Galaxy Note II N7105 Android Development] pappschlumpf:
Great, absolutely impressed, features features features!

Gesendet von meinem GT-N7105 mit Tapatalk

---------- Post added at 03:47 PM ---------- Previous post was at 03:11 PM ----------

Please keep it up, really the best feature combi for me until now! Thx

Gesendet von meinem GT-N7105 mit Tapatalk
[Galaxy Note II N7105 Android Development] jdstrydom:
Agreed. Running on f2fs filesystem, agni kernel and art. Extremely snappy with all the best features of the best ROMs. Great job!
[Galaxy Note II N7105 Android Development] pappschlumpf:
Definitly, this ROM and AGNI on f2fs, goal :)

Gesendet von meinem GT-N7105 mit Tapatalk
[Galaxy Note II N7105 Android Development] Senyaka:
Have run this over night, and thus far have not had any issues. Very battery friendly, with some nice "hidden" features like suspend actions, wakelock blocker and system app removal tucked away in the Performance tab. Features wise, all the ones I use on a daily basis, like Halo, Pie, ect, work as they should. All the apps, I normally use, work great too. Themes work. Have only had one FC with hangouts pinned to Halo, but that always happens no matter what Rom I run. So far, I am very much liking this Rom. Cheers for the work bro!
[Galaxy Note II N7105 Android Development] kpursuer:
Nice work. Smooth and one of the best featured roms out there.

T-Mobile GN2 on XDA-Premium