yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
You're not exactly out of luck. You may just have to manually repair your efs data, like you would have done before nvbackup was found.

But more than likely if you have gone this far without completely losing your imei or something, the nvbackup was done and it's doing its job restoring itself when it senses problems.

So I won't say with 100% confidence that an nvrestore won't possibly break your phone which will then need manual repairing, but I think you will be fine.

I would do the plan b backup just to cut your work down if something does happen, then do a nvrestore without doing a nvbackup.

Hope that makes sense.
[Verizon Samsung Galaxy S III] S52Stu:
Did you try this? Did it work for you?
[Verizon Samsung Galaxy S III] mastamoon:
He did and it did! :)
[Verizon Samsung Galaxy S III] Supercutetom:
Ok well here is some of my feedback. I could not get nvrestore to work for me at all. Except for one time but the fix didn't survive a reboot... Strange. Maybe I have one of these earlier models that was of concern? Anyways. These, what I'll call "Plan B" backups I have plenty of from when I first rooted my S3. I simply flashed one of those and now I'm good... For now I suppose. I'll have a little anxiety after every text I send for awhile, too.

But hey at least I don't have to use ****ing TouchWiz anymore. That **** makes me almost as mad as motoblur used to on my Droid2.
[Verizon Samsung Galaxy S III] mastamoon:
Cool, if it's working, I would now do an nvbackup to be sure you have a known good configuration to restore from. But thats just me.
[Verizon Samsung Galaxy S III] Supercutetom:
Sage-like wisdom that is. A reboot kills whatever is being fixed. During the reboot my phone will vibrate a few times and "bootloop" (it isn't really bootlooping since it eventually boots up).. Is this the bad nvbackup perhaps thinking it's "fixing" my phone? I'm

Going to reflash my good configuration while on stock and nvbackup that and I'll report back.
[Verizon Samsung Galaxy S III] Whisk_33:
I'm actually having the same problem. The SMS has been working great since. But if I press the power button to lock my phone the screen will turn black. Then turn back on. The shut down menu will pop up and then phone will start rebooting. It gets hung up during the booting process and takes a couple of tries to actually boot up again.

But the sms is working. As long as I don't touch the power button or try and restart the phone its working well. Very odd though.

Update:

Turns out my power button was just broken. I got it fixed and the phone has been flawless since.
[Verizon Samsung Galaxy S III] mastamoon:
Not a very good fix then... Meh.
[Verizon Samsung Galaxy S III] Supercutetom:
Well I cannot get anything to stick after a reboot. So I give up. I have no other guesses or options
[Verizon Samsung Galaxy S III] mastamoon:
Are you data wiping and reinstalling cm, or restoring a backup?
[Verizon Samsung Galaxy S III] Supercutetom:
I did a clean install. Scouts honor. I'm going to go through the motions one more time before I gotta head off to work and let it all settle without rebooting till I get home later tonight. I doubt that'll do much though....

It's weird how it works like it should until the phone reboots. That I don't undstand.
[Verizon Samsung Galaxy S III] mastamoon:
Did you Odin a stock package and do all this or just flash a stock based rom?

When you clean install do you just do a factory reset or do you format partitions manually?
[Verizon Samsung Galaxy S III] Supercutetom:
I avoided Odin but reluctantly gave it a go. As well as flash a stock based Rom, Scrosler's 4.3 to be exact. The stock ROMs were what I tried the first couple of times.

I have also done factory resets and formatting partitions manually just to cover my bases. I never did both the same time, though, so we're clear. Only one or the other. Never both

A side note is that upon doing an nvrestore my phone NEVER completed a reboot. I always would have to pull the battery. A couple times last night I let my phone sit for up to 15 minutes before I decided it just wasn't going to boot. I'm banging my head into a wall over this.
[Verizon Samsung Galaxy S III] mastamoon:
/me :scratches head:
[Verizon Samsung Galaxy S III] Supercutetom:
Yea it's a little bizarre. I like to think I'm being pretty thorough about the process. I'll try a couple more things later today when I get home but to be honest I don't see the outcome being to different.... I can't help but wonder if VZW really is to blame for this. The issue arose for me literally overnight. I woke, went to send a text, and it failed along with everyone after that. If it's really on VZW's end then we could be really muffed because we all know how supportive they are of us.

Anyways, sorry to clog up your thread Masta with all this.
[Verizon Samsung Galaxy S III] mastamoon:
Maybe the next step is to go back to total stock and ask vzw to send a reprovision signal. You can also do this manually by swapping a different phone number onto your phone then swap back. IIRC.
[Verizon Samsung Galaxy S III] Supercutetom:
You mean swapping SIM cards? My girl has the same phone. If that's something to try I'll give it go. She should be home before I have to head off to work.
[Verizon Samsung Galaxy S III] mastamoon:
Maybe. This might have only been possible on older non LTE phones where you could activate your phone by calling a number and typing your phone number in. IDK.
[Verizon Samsung Galaxy S III] Supercutetom:
Regardless, it's something we haven't tried yet so I'll give it go. At this point I just don't care what to try.

I wanna text, yo. I miss it and TouchWiz gives me this nasty rash on my elbows.
[Verizon Samsung Galaxy S III] mikejr83:
So I just read about 8 pages of sadness about sms issues. I'm on a pre d2lte build and my texts and MMS are working fine (with voice+). Is this problem with sms showing up on a handful of phones? Should I wait a bit on taking the next version?
[Verizon Samsung Galaxy S III] fluffman86:
I'm on Masta's 3-14 build and SMS through voice plus is working fine for me. I don't have a text plan and only use google voice, but when voice+ was broken texts were sending and receiving fine.
[Verizon Samsung Galaxy S III] savagebunny:
Question, masta will you (if possible) implement the support of the modified dalvik libraries for KitKat for the Qualcomm chipset which is possible for the N5?

Also, has there been any commits that may interfere with the Samsung network extender? I've tried two other CM11 latest builds of other devs and mine still randomly disconnects, auto switches to unknown network, and sets the network mode to 'unknown'
[Verizon Samsung Galaxy S III] fluffman86:
Ah! Mine just started jumping disconnecting and not finding a network, too. IMEI is there, then gone. There, then gone.
[Verizon Samsung Galaxy S III] neolink1:
I had the same issue, no boot after nvrestore, it stuck on the LTE screen. (I had done nvbackup previously). As others mentioned, I went to CWM and flashed the newest official nightly (3/15). No issues since.
[Verizon Samsung Galaxy S III] mastamoon:
Your able to reboot without losing the sms fix?
[Verizon Samsung Galaxy S III] neolink1:
Crap *Looks @ uptime* 35hours... Oops, I haven't rebooted since. Now I'm afraid to, lol.
[Verizon Samsung Galaxy S III] fluffman86:
Well, thought I had damaged the motherboard replacing my camera (which works correctly now), but flashed back to a 02/22 nandroid and data and voice are working. Unfortunately, I'm stuck on 1xRTT and don't have LTE.
[Verizon Samsung Galaxy S III] mastamoon:
You guys having data issues... try flashing this. http://mastamoon.truelinux.net/other/d2vzwRILlibs.zip

Its older RIL blobs from before the d2lte merge where we switched to different ones.

Edit: you may want to try these if your having sms issues also.
[Verizon Samsung Galaxy S III] fluffman86:
Flashed it. Still jumping in and out of service with Network changing from Verizon to Unknown.

And while typing this it seems to have stabilized, but I've got orange bars and no data symbol next to them. The Status page says Data: In Service but it really doesn't look like I have any. Network Type is still stuck in 1xRTT.
[Verizon Samsung Galaxy S III] mastamoon:
Have you tried changing the network mode from Global to just LTE/CDMA/EvDo?
[Verizon Samsung Galaxy S III] fluffman86:
Yes. Didn't work, unless there's something special I need to do to "apply" the settings. I just selected it and backed out.
[Verizon Samsung Galaxy S III] mastamoon:
No I think it does whatever you select on the fly, but a reboot would ensure the change is done I suppose.
[Verizon Samsung Galaxy S III] fluffman86:
The good (?) news is that I'm back on 3G / 4G (where available) because I broke one of the gold tabs at the bottom of the motherboard that connects it to the mid-frame bottom antenna. A bit of solder fixed it right up. :)

Bad news, I'm back on your 2-22-ish nightly - everything in March is disconnecting, even with your RIL patch.
[Verizon Samsung Galaxy S III] theraptscallion:
To reprovision OTA, you just need to flash back to stock ICS/JB4.1, open your dialer and dial *2767*3855#

After doing that (and odining back to ICS and downgrading my modem to match, then upgrading back up), I seem to have fixed the SMS issue, for at least one reboot, possibly more.
[Verizon Samsung Galaxy S III] mastamoon:
Hopefully it sticks and thanks for the info!
[Verizon Samsung Galaxy S III] PerCompLLC:
So I woke up this morning with the SMS bug. Everything was working fine last night. No changes to my system at all. This sucks.

Is the only solution pretty much to revert to a TW ROM and then go back to CM? Suggestions?
[Verizon Samsung Galaxy S III] mastamoon:
Check your RUIM/SIM/NV setting... had somebody elses phone 'die' overnight from this getting changed from RUIM/SIM to NV somehow.

Otherwise it looks like the fix is..

First, Flash back to stock.

Now it looks like a re-provision seems to smooth things out after an nvrestore.. but im wondering if a re-provision alone might fix. Somebody should try. If it doesnt.. nvrestore (if you have done an nvbackup or had a newer phone). Then flash back to stock to get booting.. then re-provision and move back to CM.

*** WHATEVER YOU DO, DONT LET YOUR PHONE OTA update! ***
[Verizon Samsung Galaxy S III] PerCompLLC:
I'll try the "re-provision" fix. I've already messed with RUIM/SIM and NV - it was indeed set correctly. What is interesting about this is that everything was working perfectly yesterday. I text quite a bit with my wife and would have noticed right away if there were a problem. This morning I woke up the the bug without any changes to my system.

Should I ODIN? Or just flash a TW based ROM. Does it matter?
[Verizon Samsung Galaxy S III] mastamoon:
I would probably odin back to an early TW rom, [MENTION=1553070]theraptscallion[/MENTION] says TW/JB4.1 build for re-provision... but I don't know if later builds are totally unable to re-provision.

Let us know how it works out.. taking the nvbackup/nvrestore part of the equation would be a much better/easier fix.
[Verizon Samsung Galaxy S III] PerCompLLC:
Sounds good. I won't get to it until tonight as I'm stuck in a class for work all day. Sucks because I'm stuck with the SMS bug until I get home.
[Verizon Samsung Galaxy S III] ef-civic:
Masta, do I need to install the firmware along with the latest modem or can I just do the modem
[Verizon Samsung Galaxy S III] PerCompLLC:
Deleted
[Verizon Samsung Galaxy S III] mastamoon:
Install the firmware first(which contains an older modem), then the new modem zip. If your talking about the files from the OP anyway.
[Verizon Samsung Galaxy S III] ef-civic:
I did Odin back to stock so I'm on LF2. So use the same procedure?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah if you are coming from an old stock rom and looking to go CM again.. first you do the whole root/unlock procedure to get CWM installed.. then you would install the firmwares, factory reset and install CM.

I think thats it. :)
[Verizon Samsung Galaxy S III] ef-civic:
I already have CM11 installed. Just the modem?
[Verizon Samsung Galaxy S III] mastamoon:
Oh, if you have CM installed, but never updated the firmware/modem.. then just flash those 2 files and reboot. You need the MF1 firmware along with the ML1 modem. If you came from an old odin build, that means you still are using that builds firmware and modem. Modem alone isnt enough.
[Verizon Samsung Galaxy S III] johnwaco:
I flashed a 4.3 stock rooted ROM and was unable to reprovision. Was told call could not be completed. I did do an nv restore from cm11. When it did the reboot I held volume up and the home button to go to recovery. Then flashed one of your builds and gapps. SMS works. Have not tried to reboot so I don't know if it sticks.
[Verizon Samsung Galaxy S III] BrwnSuperman:
I was getting the SMS bug where I'd have to toggle airplane mode between messages. Can anyone share their copy of LF2? Going back to JellyBean stock and reprovisioning didn't fix it.
[Verizon Samsung Galaxy S III] mastamoon:
That stinks. I guess the nvrestore part is vital.

Check Sam-mobile.com or samsung-updates.com for stock firmware.
[Verizon Samsung Galaxy S III] BrwnSuperman:
Both of those sites are no longer hosting old firmware like LF2 for the D2VZW. I'm going to try MB1.
[Verizon Samsung Galaxy S III] Stealth111:
AHHH, the dreaded Network Extender. I am afraid that I am in the same boat. I have been on CM since version 9. I love everything that CM offers! Unfortunately, there has really been no support directly for our extenders. The mere fact that they still work for us has been awesome. A few builds, back in the 10.2 era, had some extender issues, but nothing like what I have been through on 11. I am now at a point that I have the dreaded MMS issue, but ONLY when connected to my Network Extenders. Going back to TW puts everything back to working perfectly, always has... I really don't want to be there though. I would love to be back to CM. I have asked for help in IRC, submitted logcats, but it does not seem like it is going to get resolved for me anytime soon. I have been all over the place with these CM builds, from losing my IMEI and everything in-between, but ultimately things seemed to get worked out eventually. Hopefully one day I will be able to once again come back to CM, and actually have a phone that I can use on a daily basis... :(

Odin'd back to stock 4.04

NVrestore

reprovisioned

New Sim Card

Stock working fine.

Full clean install to latest CM Nightly, no MMS on Extender, otherwise fine. Nandroid back to previous CM install, same, not working. (No APN selected for this device)

Nandroid back to TW 4.3 (old and slow's) MMS is fine , just like stock.

Back to another wipe, clean install of CM, no MMS on extender. (No APN selected for this device)

Nandroid back to TW 4.3 to stay for a while.

^^^ not a happy camper.......
[Verizon Samsung Galaxy S III] Whisk_33:
http://xdaforums.com/showthread.php?t=1762204

This thread has the stock image with root (so super user is included).

I've got a broken power button but everything else seems to work well for me. If anyone knows a good place to send my phone for the repair, I would appreciate the PM. Thx.
[Verizon Samsung Galaxy S III] theraptscallion:
I can't understand why, since reprovisioning should overwrite the nv information, which is why people stopped doing QPST injections if they lost their IMEI.
[Verizon Samsung Galaxy S III] V3TTOO:
Hey, I did a clean install of yesterday's build, but I have been having some issues for some time now. I can't seem to get anything to connect to the mobile hotspot anymore. I tried on my laptop and it will say connected then disconnect and try again. Only on the mobile hotspot. It worked in January, not sure if I used it in Feb.
[Verizon Samsung Galaxy S III] PerCompLLC:
nvrestore

Masta (or anyone else) - does nvrestore only work on TW? I did an nvbackup way back when. I'm just curious.

Edit: Disregard. I searched through all the info I have and see that nvrestore on AOSP ROMs tends to result in a bootloop. It is recommended to go back to TW, nvrestore, and then restore a CM backup. That's what I'll do.

How does one reprovision a VZW SGS3? I'm trying to fix the SMS bug.
[Verizon Samsung Galaxy S III] mastamoon:
dis
[Verizon Samsung Galaxy S III] PerCompLLC:
Thanks Masta!
[Verizon Samsung Galaxy S III] Hans5849:
Hey masta, I keep getting a crash when I'm using Handcent group messing. I've submitted a log cat to the developer but I thought I might submit one to you too. As I have no idea what the data means.
[Verizon Samsung Galaxy S III] korky888:
Help

Hi Guys,

Please help. I loaded the latest update. Now the phone stucks at boot animation. I am not able to get into recovery because my down volume key is broken. What to do?

Thanks in advance
[Verizon Samsung Galaxy S III] PerCompLLC:
Recovery is your up button. Battery pull, volume up button / home button / power button.
[Verizon Samsung Galaxy S III] korky888:
Great. Thank you! I am in. For some reason I remember it is down button.
[Verizon Samsung Galaxy S III] PerCompLLC:
Okay folks... If you have the SMS bug, nvrestore doesn't appear to be necessary. I backed up to external sd card, ODINed back to rooted stock, reprovisioned, loaded rom manager, and restored my backup. SMS appears to be back to normal.

Edit: Guess it doesn't survive reboots... :(
[Verizon Samsung Galaxy S III] mangler1055:
Say we don't have a backup... Or a windows machine.

Ideas for fixing the SMS problem?

I stopped doing backups since it's faster to do a clean install and titanium... Than to wait for a nandroid backup/restore.
[Verizon Samsung Galaxy S III] mastamoon:
Nice. Glad it's working for you.. Has the fix survived some reboots?
[Verizon Samsung Galaxy S III] PerCompLLC:
:( unfortunately, no... Just rebooted and tried again. Any suggestions?
[Verizon Samsung Galaxy S III] mastamoon:
Think thats where the nvrestore comes in.
[Verizon Samsung Galaxy S III] PerCompLLC:
Okay, I'll give that a try. I purposely didn't nvrestore to see if it would work without. Back to the drawing board... I'll report back later.

---------- Post added at 06:12 PM ---------- Previous post was at 05:48 PM ----------

Ya. Down button / home button / power button is to get into download mode (for ODIN for example).
[Verizon Samsung Galaxy S III] jalewis:
BTW, I tried doing just an nvrestore and reflash of the rom, without going back to stock. It worked until I rebooted...
[Verizon Samsung Galaxy S III] PerCompLLC:
I just did an Odin back to stock, nvrestore, then I had to Odin again because of the bootloop, then I restored my backup. SMS is working, but I'm afraid to reboot now...

Edit: after a reboot SMS still works!
[Verizon Samsung Galaxy S III] PerCompLLC:
So I'm wondering if the problem has to do with the ML1 radio. Yesterday after the fix above I was on the MF1 radio package. This morning I flashed the ML1 modem (because that is what I've been using for quite awhile). And, after the reboot, SMS was borked again.

So here is what I did:

- Flashed the MF1 radio (because I think ML1 just "might" be the problem)

- Backed up current ROM (CM11)

- nvrestore while on CM11 - my reasoning was that since both AOSP and TW will bootloop after nvrestore, what's the difference?

- Battery pull (because of the bootloop)

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

- Restored stock image (because now I have a backup after doing this 4 times)

- Dialed *2767*3855# (to reprovision)

- Booted back into CWM and restored my CM11 backup

SMS works once again! And the fix held after a reboot! I'm going to stay off of ML1 for several days and reboot multiple times to see, but so far so good...

I hope this helps someone!
[Verizon Samsung Galaxy S III] mastamoon:
People have run the ml1 modem for months now, why all of the sudden?

Not saying your wrong or anything, it's a good thought, but why!!?? :-\ :)
[Verizon Samsung Galaxy S III] PerCompLLC:
Yeah, I dunno. I've been running ML1 since the first day invisiblek separated the firmware from the modem and released it. And I have no idea. Maybe VZW has changed something that actually checks firmware to make sure it all matches? Like I said, I'm going to stay on MF1 for a few days and go through multiple reboots to see if SMS continues to work. Maybe we should do a poll to see if everyone that got hit with the SMS bug was on ML1... Just a thought.
[Verizon Samsung Galaxy S III] mastamoon:
Ml1...no sms bug. :)
[Verizon Samsung Galaxy S III] PerCompLLC:
You suck! :silly:

---------- Post added at 10:12 AM ---------- Previous post was at 09:45 AM ----------

SMS fix just survived it's second reboot. Still on MF1 firmware. I really think that ML1 might have something to do with it. But of course I have absolutely no idea why...
[Verizon Samsung Galaxy S III] Rig24:
On 2/14, ML1 radio, stock kernel. Haven't made a change and started getting the SMS issue yesterday. But now today, no problem. Very odd.

---------- Post added at 12:25 PM ---------- Previous post was at 12:11 PM ----------
[Verizon Samsung Galaxy S III] mastamoon:
Try going back to the mf1 modem/firmware.
[Verizon Samsung Galaxy S III] TwistingSoul:
So, for a while, I was flashing the separate Google dialer app to have the ability to search nearby businesses and such by typing in "pizza" for example.

With the fixes in the latest release, I don't need to do the separate dialer app, however the Google dialer phone icon is still on my home screen, and it says it's not installed when I try to launch it.

How can I get rid of that without having to manually remove the shortcut to that no longer installed app every time?
[Verizon Samsung Galaxy S III] Rig24:
Switching to mf1 worked... So far
[Verizon Samsung Galaxy S III] mastamoon:
Surviving reboots? Didn't do anything else?
[Verizon Samsung Galaxy S III] Rig24:
Worked for 5 minutes and back to toggling airplane mode.
[Verizon Samsung Galaxy S III] mastamoon:
Too good to be true. :-\
[Verizon Samsung Galaxy S III] PerCompLLC:
Mine is still good after 4 reboots.
[Verizon Samsung Galaxy S III] Zacharybinx34:
I heard you weren't going to be doing these, did you change your mind or?
[Verizon Samsung Galaxy S III] AdMire:
Thank you, that was driving me crazy!
[Verizon Samsung Galaxy S III] mastamoon:
Cuz the alternative methods I was going to use became a logistical nightmare.
[Verizon Samsung Galaxy S III] senorbuck:
Masta, any idea what from the latest official 12/16 build borked the camera? The camera display (cam and video) is all black. It's awesome :P Looked at the changelog but I can't make much sense out of some of it.

Gonna roll w/ your latest for the time being.
[Verizon Samsung Galaxy S III] Chris123NT:
#blamenard

Updated adreno blobs borked it AFAIK
[Verizon Samsung Galaxy S III] mikejr83:
Got stood up again even after toggling NFC. Made sure to try it at readers that I knew worked prior to 4.4. Oh well. I guess I'll live without wallet for a bit.
[Verizon Samsung Galaxy S III] RED ZMAN:
Hey Masta, I just wanted to say thank you for all of your hard work on the Samsung Galaxy s3. You made that phone one of the best phones I've ever owned, and other than the Bluetooth bug you really worked everything out that I use daily. I bought a Nexus 5 a month ago, and have been testing out Straight Talk wireless to leave Verizon. I'm pretty happy and stable over here so just wanted to let you know I've been following your cm 11 progress and I appreciate you continuing your work. When I sell my SGS 3, it will have your cm 11 on it. Thanks for all the hard work.

Going to donate you 50 bucks.
[Verizon Samsung Galaxy S III] PerCompLLC:
So it appears that beginning with the 12/15 unofficial (Masta hasn't released yet so I rolled my own), it is now not possible to hide the battery icon. You can toggle it off but when the screen turns off and then back on the icon is back, albeit smaller. The same issue is present in 12/16. Problem didn't exist on 12/14.

FYI, the reason I noticed is because I prefer to use team battery bar for my battery display.

Not looking for a fix necessarily, just wondering if anyone knows what happened.