yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] MWFD:
Uh oh so does this mean NFC is not working? I beam tons of files and hope thisbisnt affected but haven't been able to test myself yet.

EDITED: Just tested and sending from GS3 to Nexus 7 (2013) worked without any issues, but this is 12/14 build.
[Verizon Samsung Galaxy S III] thelangosta:
I think it is just Google wallet he was talking about.

Sent from my Transformer TF101
[Verizon Samsung Galaxy S III] dandydon414:
yeah for coders perhaps, but not for guys like me who just want to insert my own images
[Verizon Samsung Galaxy S III] locozildjiangodx:
Is the snapchat issue something that is ROM related or app related or what? I GOTTA SEND MY SELFIES
[Verizon Samsung Galaxy S III] TwistingSoul:
I'm about to install the build from today (12/16/2013) and noticed you have a Kernels folder on your truelinux.org page, Masta.

Are those kernels different than what comes packaged with the ROM itself, or are those equivalent to others such as BMS/LeanKernel/etc?

If the latter, is there a changelog of what those do?
[Verizon Samsung Galaxy S III] mastamoon:
Doesnt work in any CM11/AOSP rom I dont think, for d2vzw anyway.

No, the kernel directory is for one offs that I do for certain things.. you can ignore that folder unless I link it somewhere.
[Verizon Samsung Galaxy S III] PerCompLLC:
Fyi, this is present in today's build as well (Masta's 12/16 unofficial).
[Verizon Samsung Galaxy S III] goldsmitht:
How is the camera in 12/16? Does it have the problems reported on the official forum? Or at least what I thought I saw on official?
[Verizon Samsung Galaxy S III] senorbuck:
Camera works. Looks like Mastamoon reverted the bad stuff.
[Verizon Samsung Galaxy S III] V3TTOO:
Hey, has anyone had issues with BT not connecting? It was working well with 12/12, but had issues with 12/14. I just updated to 12/16 and it seems to be ok for now. Just wondering if it was just me.
[Verizon Samsung Galaxy S III] mikejr83:
Yep, just Wallet appears to not work. I use Trigger and all my NFC tags work.
[Verizon Samsung Galaxy S III] mastamoon:
Bluetooth was broke on official and some unofficials over the weekend. I don't think any of my builds were effected though.
[Verizon Samsung Galaxy S III] mastamoon:
You did the other stuff also. Might be necessary to fix the issue along with the modem. And hopefully the modem keeps the issue from popping up again.
[Verizon Samsung Galaxy S III] PerCompLLC:
That's what I'm thinking as well...
[Verizon Samsung Galaxy S III] ef-civic:
I found the MF1 firmware but not the modem. Dies anyone have a link to where I can download that file
[Verizon Samsung Galaxy S III] mastamoon:
The mf1 firmware package contains the modem also. The ml1 modem package contains just the modem. That's why you had to flash one over the other.
[Verizon Samsung Galaxy S III] ef-civic:
OK. I will flash and post results
[Verizon Samsung Galaxy S III] ef-civic:
Did not work after numerous reboots...... :-/
[Verizon Samsung Galaxy S III] mastamoon:
You did the repair process with the mf1 modem in place? Still ended up breaking again?
[Verizon Samsung Galaxy S III] ef-civic:
Do not know how that is done
[Verizon Samsung Galaxy S III] PerCompLLC:
Assuming that this is for the SMS bug... Try the following:

**Note, order is important. You must nvrestore BEFORE reprovision.

- Back up current ROM (CM11) to external sdcard. This is important because you will lose your internal storage if you ODIN.

- Copy anything you want to keep from internal storage to your computer (or to your external SD card)

- nvrestore while on CM11 - Only do this if you have done an nvbackup while everything was still good or if you have a newer phone.

- Battery pull (because you will bootloop after nvrestore)

If you have a TW backup (note that it must be 4.1):

- Volume up/home button/power button to get into CWM.

- Restore TW backup.

If you do NOT have a TW backup

- Volume down/home button/power button to get into download mode

- Run ODIN and restore a stock image of TW (must be 4.1 - I use the original route 66 because it is already rooted - posted below from my Dropbox)

- When it reboots you will once again bootloop

- Battery pull, volume up/home button/power button to get into stock recovery and do a data wipe/factory reset.

- Boot up into stock TW.

- Reboot again (because for me, SU doesn't work properly until a reboot - and you will need root access to flash CWM through ROM Manager)

Finally

- Dial *2767*3855# (to reprovision)

- Login to the play store and download and install ROM Manager

- Flash CWM recovery

- Reboot back into CWM and restore your CM11 backup from the external SD card.

This worked for me... Your mileage may vary.

** If you want/need to learn how to use ODIN, go here: http://xdaforums.com/showthread.php?t=1722686

** If you want/need the stock root66 ODIN file, here is the link: http://mastamoon.truelinux.net/other/stock.vzw_root66.tar (after you install, do NOT accept the VZW update. Defer and then perform the other steps)

Finally, do NOT upgrade to the ML1 modem. It appears that the ML1 modem may cause the SMS "fix" not to survive a reboot. However, on the MF1 firmware, the SMS "fix" appears to stay intact.

Hope this helps!
[Verizon Samsung Galaxy S III] mastamoon:
Thanks for the detailed instructions man, appreciate it.
[Verizon Samsung Galaxy S III] PerCompLLC:
Note that I have made a couple of "clarification" edits. So you may want to go back and re-read if you are unclear about anything.

Masta, feel free to modify/repost any of these instructions in the OP if you like. I know a LOT of folks are asking about the SMS bug on AOSP.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thank you so much for the helpful instructions! I'm going to tackle that today on my phone. Did you need to unlock the bootloader again at any point?
[Verizon Samsung Galaxy S III] PerCompLLC:
Not if you ODIN with the root 66 tar. Not sure about others.
[Verizon Samsung Galaxy S III] Hybridnoob:
Worked great! The only thing I would clarify is it appears TW 4.1 won't provision. The linked 4.0 file works like a charm though. SMS is working again so far. I would also add to flash the MF1 firmware once you restore your backup.
[Verizon Samsung Galaxy S III] PerCompLLC:
Glad it worked for you! Note that if you didn't nvrestore, the fix will not survive a reboot (at least it didn't for me). Just an FYI.
[Verizon Samsung Galaxy S III] Hybridnoob:
The fix didn't keep for me before even a reboot (several failed SMSs)... Toggling airplane mode temporarily allows SMS to send. I did nvrestore prior to multiple Odins. Should I have nvrestored after doing the Odin? I'm not sure of any other options or fixes...

It's not a big enough deal to switch to TW, but I hope the Devs can figure it out one day.
[Verizon Samsung Galaxy S III] PerCompLLC:
Very interesting... I documented the steps as I did them and I'm now in day two of a "fixed" SMS bug. I've rebooted a total of 10 times.
[Verizon Samsung Galaxy S III] Stealth111:
I wish I could be so lucky. I odin'd back to stock, re-provisioned, nvrestore, fresh install of latest nightly, MF1, And I still get the dreaded "No APN" error, BUT only when I am connected to my Network Extender though. Still, at home and especially at work (all day) I am ALWAYS on extenders. I have no choice to go back to TW 4.3 where the problem does not exist(Old and Slow's version). Not having it working on CM affects my ability to do my job... :(

I will hang out trolling the forums and irc hoping that a fix may come one day..
[Verizon Samsung Galaxy S III] PerCompLLC:
I think I know your problem based on your description ... Nvrestore before you reprovision. I think that is the key. Worth a try anyway...

That said, I never had any apn issues. Only the SMS bug...
[Verizon Samsung Galaxy S III] mangler1055:
I have the SMS bug and have a few questions.

I only have a mac, so no windows machine to use ODIN. Can i do this using mobile ODIN?

Not sure if pulling the sim card or maybe airplane mode would do anything to help.

If no, other ways to do ODIN or go back to stock? Can i just flash a TW rom after the nvrestore and not do a root66 ODIN?

Also, do other 4.4 roms like Liquid or Carbon have the SMS issue, or just CM?
[Verizon Samsung Galaxy S III] pcwizkid1994:
Would I be able to flash this? I am rooted on 4.3 and when I boot up I have a Samsung logo with a unlock icon.??
[Verizon Samsung Galaxy S III] mastamoon:
If you took the 4.3 Ota or just got your s3 with 4.3 pre-installed.. No.
[Verizon Samsung Galaxy S III] pcwizkid1994:
Are there any roms I could flash then?
[Verizon Samsung Galaxy S III] Hybridnoob:
Maybe CleanROM? It's based on stock.
[Verizon Samsung Galaxy S III] mastamoon:
I don't think there is much you can do on rooted stock besides debloat.
[Verizon Samsung Galaxy S III] mangler1055:
Masta, thoughts on this?

Thanks.
[Verizon Samsung Galaxy S III] mastamoon:
Can't you use heimdall?
[Verizon Samsung Galaxy S III] mangler1055:
I'm trying that right now... the root66.tar file is grayed out when i try to select it from the Heimdall Firmware Packate browse button.

I'm gonna read a bit more about using Heimdall.
[Verizon Samsung Galaxy S III] mastamoon:
Might have to extract the stuff from the zip maybe? I have no experience with heimdall.
[Verizon Samsung Galaxy S III] Supercutetom:
I am now on my 3rd reboot and so far my SMS is still functional. I haven't flashed a new modem yet so I'll see how that plays out... If it all works out OK it'll be a godsend.
[Verizon Samsung Galaxy S III] PerCompLLC:
I'm afraid that I don't know anything about mobile Odin... And any TW ROM should do as long as it's 4,1. Finally, as far as I know, all AOSP based ROMs are experiencing the SMS bug in one way or another (but I'm not 100% sure on that).

If you do try my fix, order is important. Nvrestore before reprovision.

Good luck!
[Verizon Samsung Galaxy S III] zachf714:
Only aosp based Roms that merged the qcril changes or are using the cm telephony repos have the problem. You can check by going to their github and finding their /android repo or /platform_manifest repo, make sure it's on a KitKat branch and look in default XML for frameworks opt telephony , if it's the cm repo it has the problem but if it is not, it may or may not have the problem, you will have to check the git history . a good example is aokp does not have the problem because they have not merged qcril and I believe PAC has not either
[Verizon Samsung Galaxy S III] ef-civic:
can this be done in mobile odin?
[Verizon Samsung Galaxy S III] Hybridnoob:
What about this? It's web-based and should be platform independent. I haven't tried it, but the devs behind the website are well known and highly respected in the rooting community. I'd love to hear if it works though.

http://casual-dev.com/2014/01/04/jodin3-web-browser-or-offline-flashing-tool/
[Verizon Samsung Galaxy S III] mangler1055:
I dusted off my 10 year old dell and used the regular Odin.

Things seemed fine when I flashed a carbon nightly... But in general the rom was unstable.

Back on the latest nightly from this thread and I can't even get the one SMS out per boot/airplane toggle that I was getting before.

I made a nandroid backup of the root66 state.. So I'll try again when I get a moment

Thanks everyone for your input.
[Verizon Samsung Galaxy S III] PerCompLLC:
Did you do an nvrestore and then a reprovision? These steps are indeed necessary before you load CM up again.
[Verizon Samsung Galaxy S III] Obaterista93:
Huge thanks to PerCompLLC for the writeup, works wonderfully. Glad to be back on AOSP now. Does anyone know if this fix persists across multiple flashes? It survives reboots, but I haven't tried flashing anything after the fix was verified working.
[Verizon Samsung Galaxy S III] PerCompLLC:
Glad it worked for you!

It does indeed! I just rolled a new build from today and flashed it. SMS is still working perfectly for me.
[Verizon Samsung Galaxy S III] mangler1055:
Yes, i did the nvrestore and the reprovision. Turned out i had some mobile settings wrong, but the SMS was still one at a time...

then all of the sudden i couldn't take or recieve calls. IMEI SV was 00 at at that point. Tried the nvrestore and the reprovision again.. flashed back to CM11.. and still only 1 SMS per airplane toggle.

Going to try AOKP and hope for the best.

Thanks for your guide.

---------- Post added at 02:36 PM ---------- Previous post was at 02:30 PM ----------

Hmm.. my root66 nandroid seems to be missing. does the reprovision happen to wipe internal memory?
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
To everyone who is trying to get SMS back: Do the nvrestore method but don't flash a new modem after, I believe that's why it's not working for you. I've had my texting working for a day now with multiple reboots. I didn't flash a new modem and I've had 0 connectivity issues.
[Verizon Samsung Galaxy S III] mastamoon:
I've preemptively flashed back to the mf1 firmware and will probably pull the ml1 modem zip from the OP till this issues blows by.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Are people feeling like the 1 sms issue is specifically with the VRUCML1 modem?
[Verizon Samsung Galaxy S III] mastamoon:
Don't know for sure. Has been fine for months and months.. Idk.
[Verizon Samsung Galaxy S III] Hans5849:
It seems the current rom is corrupted and can't be downloaded
[Verizon Samsung Galaxy S III] mastamoon:
Hmm.. Try via pc? I've had a problem lately with the downloads on my phone stopping and starting again a few times, but thought it was just me.
[Verizon Samsung Galaxy S III] BrwnSuperman:
I can confirm this works. I tried it with other modems and I had the ML1 modern since it came out but started getting the SMS bug like many of you. MF1 + stock + reprovisioning = fix. I tried it without MF1 with no success, also without reprovisioning with no success. I did do a completely clean install instead of restoring, everything is running great. Thanks
[Verizon Samsung Galaxy S III] Supercutetom:
It is interesting how finicky this SMS issue is for everyone is. For me it seems to be fixed but only if I leave the modems alone. I've tried all sorts of combinations with the modems but only if I leave it on stock does my SMS work. I'm glad that it is at least "fixed". Even though it doesn't quite feel fixed since I'm stuck on older modems,rpms,etc I'll get over it to stay off TouchWiz. Nevertheless thank you all who have helped.

Also, I think for awhile I'll always get a hit of anxiety when I send an SMS.
[Verizon Samsung Galaxy S III] PerCompLLC:
SMS Fix...

All, Dropbox suspended my public hosting due to excessive traffic from folks downloading the root 66 TW rom for the SMS fix (who knew?). I have removed the file in order to get my Dropbox working again.

Anyway, I have made the file available to Masta and we will be relinking it later today if anyone needs it.

Just an FYI...
[Verizon Samsung Galaxy S III] mastamoon:
Ive added the directions to the OP along with the link to the file. :good:
[Verizon Samsung Galaxy S III] neolink1:
Thanks everyone... MY SMS issues also seem to be resolved after following what [MENTION=2492427]PerCompLLC[/MENTION] outlined.
[Verizon Samsung Galaxy S III] PerCompLLC:
Glad it worked for you!
[Verizon Samsung Galaxy S III] ef-civic:
Seemed to have fixed my problem too. Thanks PerCompLLC
[Verizon Samsung Galaxy S III] neolink1:
Is anyone flashing new nighties or pretty much staying put... Any SMS issues with new-er ones?
[Verizon Samsung Galaxy S III] PerCompLLC:
I'm on 3/26 (my own build). No SMS issues since I "fixed" SMS through nvrestore, reprovisioning, and downgrading the firmware/modem to MF1. That said I will not be upgrading my modem to ML1 anytime soon as I believe that to ultimately be the culprit in my opinion.

So far I have flashed two new builds since the "fix" and haven't had any issues at all.
[Verizon Samsung Galaxy S III] neolink1:
That's great news, thanks... I'm also sticking to MF1 for now. Service seems to be a bit worse with it, but it's worth it to have SMS.
[Verizon Samsung Galaxy S III] neolink1:
So, I may be having the issue again :(

That said, I just went through the process, and I have a question about it. When you do the following step:

- Dial *2767*3855# (to reprovision)

My phone doesn't actually dial out. It immediately states "factory reset" and it reboots and does it. Did you also experience this? This is the only thing I can think of. I'm doing everything to the letter, and IMEI seems intact. 3/25/14 Masta nightly, with MF1. (No issues on TW).

And, my flashing order to get back to CM (clean flash) is:

1 ROM

2 GAPPS

3 MF1 FIRMWARE

4 Clear data/factory reset.

From my understanding... I should NOT be dialing Dial *228, right?
[Verizon Samsung Galaxy S III] PerCompLLC:
"Reprovision" is basically a complete factory reset + more. You did indeed do it correctly. And yes, DO NOT dial *228. For many this has fried their SIM card and they have had to request a new one.
[Verizon Samsung Galaxy S III] billquinn1:
I'm sure you just miss typed but you don't clear system after flash. You'd have no ROM.
[Verizon Samsung Galaxy S III] jkabaseball:
I'm in the same boat. I haven't had this issue, but want to flash back to old firmware. Can I just download the zip and flash in CWM?
[Verizon Samsung Galaxy S III] Hybridnoob:
Yes, that's correct.
[Verizon Samsung Galaxy S III] neolink1:
Yeah, sorry it was late... Wipe data/factory reset :)
[Verizon Samsung Galaxy S III] neolink1:
[/COLOR]

Unfortunately, I was still having issues... So I thought to try something a tad different with the modems... Let me ask this question:

When you guys flash the modem, do you flash the full firmware for MF1? (http://mastamoon.truelinux.net/firmw...1_firmware.zip). I went through the entire process once again, and it seems I can make it into CM11 and text non-stop on VRLF2, which is stock when you go the odin root66 route

EDIT1: Ok, after succsfully testing with VRLF2, I thought I'd update to the recommended modem/firmware... So I did, and flashed MF1 from above link. However, on boot of CM I did see a "new sim card" detected message, which said reboot. I ignored it and I can text back to back so far. Time to reboot and see if it "sticks". I have not seen this message previously.

EDIT2: Ok, so rebooting after the above sim card message... Broke it, I can only text one at a time then airplane mode is required to text again

EDIT3: If I go back through everything again, and stick with the old VRLF2... Which seems to work, are there any other possible issues from using an old modem?

Finally, if I shouldn't stay on VRLF2, which seems to be the only way to make this work with CM for me... Are there any TW roms you guys recommend? (I was thinking this one) Otherwise, I'm just going full stock as I'm at my wits end now :(
[Verizon Samsung Galaxy S III] PerCompLLC:
For the record, I installed the complete MF1 firmware package (zip install provided by invisiblek). Haven't had a problem since. This was after nvrestore and reprovision. I am now on 3/28 cm11 nightly.

MF1 zip install: http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm glad (and sorry) I'm not alone. I had the same experience when I tried that process again yesterday. I did the whole process and clean flashed, so I know it wasn't my backup. I followed the instructions verbatim.

I did discover a workaround that seems to be working so far - use Voice+.

For TW, I recommend CleanROM, which is by the same Dev you linked to.
[Verizon Samsung Galaxy S III] Stealth111:
Yeah, finally got my "No APN" issue sorted, should be merged shortly into nightlies... :) My sms and mms are all good, even on ML1!
[Verizon Samsung Galaxy S III] Hybridnoob:
That's awesome! I'm very curious to know what was wrong and what fixed it.
[Verizon Samsung Galaxy S III] Stealth111:
I was getting an error popup on my screen whenever I went to send an mms message or trying to authenticate certain Verizon Apps. It would say "No APN specified for this device". The message would not go away until a reboot. It would also not allow me to send the message, or receive one. The problem was that I have Verizon Network Extenders at my house, and all over at my job. When connected to a Network Extender, it uses an APN of 31000 (mcc "310" mnc "00"). These value didn't exist in the current unified apns-conf.xml file. When I used a modified file with those values added, the problem immediately disappeared. The change has been added into the next nightly that will drop tonight.
[Verizon Samsung Galaxy S III] neolink1:
I thought I had a temporary solution from something PerCompLLC mentioned, as I had working SMS back to back on MF1... It survived a a reboot or two, but sadly it's broken again. So, I guess I'll try a few more things... Or, just go back to TW. (Which I want to avoid like the plague).
[Verizon Samsung Galaxy S III] samsgun357:
For what its worth, I've never updated to ML1 from MF1 and I am experiencing the SMS bug. Seems like it all started when ROMs went to the universal d2lte builds. May be just a coincidence, idk???

Are other d2 variants experiencing this or is it vzw specific? What about note 2/3 or gs4's?

Watch, as I combine all the juice from my mind...
[Verizon Samsung Galaxy S III] iamrazor:
This was my suspicion as well. It seemed as if once it was d2lte I was seeing constant random data drops even at work (excellent LTE coverage ).

I've gone back to mastamoons 1.17.14 for moar solidity....
[Verizon Samsung Galaxy S III] Supercutetom:
Hey guys I seriously doubt it has ANYTHING to do with this. I was on CM 10.2 stable when the SMS issue hit. Litterally any AOSP rom that I flashed would not work at all. Period. No matter how far back I went for versions of various ROMs. This is an issue with Verizon. Otherwise way more people would have this problem. It wouldn't be such a fragmented issue.
[Verizon Samsung Galaxy S III] PerCompLLC:
Extra Gain on Calls

Anybody know where the option box for "Extra Gain on Calls" is? I knew where it was earlier in the nightly cycle, but I think it's been moved.

Thanks!
[Verizon Samsung Galaxy S III] zachf714:
Umm I'm on my own aokp KitKat builds. Working on unified builds and I have no SMS problems ... It has to do with the way the qcril stack was written for 4.4. It obviously is setting the wrong permissions for the radio causing a corruption of /efs on boot

Edit - also aokp does not have qcril so it is qcril related
[Verizon Samsung Galaxy S III] Supercutetom:
I apologize. I wasn't trying to start an argument. We have enough of those on the Internet already... It's just that I was on a 4.3 ROM when the issue hit my phone. I had done no flashing prior to the issue as well and I had been on my current ROM for a few weeks. All I did was wake up one morning and my SMS would just not send at all.
[Verizon Samsung Galaxy S III] zachf714:
No arguing, I was being a d*ck . but I am kind of confused on how it started on 4.3 ... Maybe your Sim settings changed which happens
[Verizon Samsung Galaxy S III] Jaegermeiste:
Fair warning: FWIW (and I know that it's not officially supported) but Masta's 4/1 nightly breaks ART hard. Boots, but a never ending stream of force closes regarding Themes, NFC, and InCallUI prevent access to anything. Reverting to 3/29, everything is awesome.
[Verizon Samsung Galaxy S III] greekstile:
Do you mean it has been fixed in the official CM nightlies or Masta's builds? Or both? I also have been having this issue.

Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
Is it broken on official?
[Verizon Samsung Galaxy S III] PerCompLLC:
Yup! At least that is what's being reported on the official thread.
[Verizon Samsung Galaxy S III] greekstile:
I should add, it's NOT fixed in today's build. Do you have a copy of the modified apns-conf.xml file you might share? Really tired of MMS not working while connected to the extender...
[Verizon Samsung Galaxy S III] ef-civic:
Installed 0401 today and no text messenging again :(.

I did not change anything other than that. All too weird....
[Verizon Samsung Galaxy S III] wolficus:
are there no updates on the unofficial past 3-25?

not complaining mind you.. just curious. 3-25 is doing me well.. beisides a couple camera hiccups.