yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Whisk_33:
Correct. I didn't have one so I had to use the ODIN method, but I believe the non ODIN method is what PerCOMPLLC used.

I would gladly update the OP, but the 120 post doesn't have any new information. It uses a method of manually downgrading/moding the bootchain etc. which should all be included on the root.66 tar in the link included in the OP. The 120 post also includes some text sensitive commands that I just don't want someone crying foul because they didn't double check their command prompt. And post 120 is a lot longer...

Again, if something needs to be updated/changed in the OP please let me know. I do want it to be accurate and terse.

Glad it worked for you. That is the point.
[Verizon Samsung Galaxy S III] Fivecent:
Wanted to report that the method in the OP worked on SlimKat 4.1.

The only difference is that instead of getting CWM through Rom Manager, I flashed TWRP via Odin after the re-provison and then restored my backup through that.

Edit: I upgraded to BMF1 Firmware and a few hours later SMS cut out again. I'm going to try the process again without upgrading and see what happens.
[Verizon Samsung Galaxy S III] net-cat:
Update: I have since updated my radio to VRBMB1 and haven't had the problem return. (As I recall, this was the OTA 4.1 radio, but I could be wrong.) It mostly seems to be a problem with later radios.

As for what I posted in #120, I'm glad it's working for people. The critical thing in that procedure seems to be reverting the radio back to an earlier version more than anything else.

(Geez, I had to cycle through about five captchas before I got one I could decipher.)
[Verizon Samsung Galaxy S III] NMEAGENT:
Anyone try to only flash the radios instead of going back to TW?
[Verizon Samsung Galaxy S III] net-cat:
I'm curious about this, too.
[Verizon Samsung Galaxy S III] tech9tcv:
That does NOT work.
[Verizon Samsung Galaxy S III] lv128:
I did try the OP method, but no luck there, it would work for about an hour, then fail again until I rebooted, then it's back to 1sms, I've flashed the phone probably about 30+ times during the past two months.
[Verizon Samsung Galaxy S III] Whisk_33:
Did you try using the root.66 file or did you have your own nandroid that your were restoring? This is the first I have heard of this method not working.

My understanding is that going back with ODIN puts everything in the phone (firmwares and modems) back to day one, and this process paired with the refreshing of settings has been a permanent fix for people as long as they don't update the firmware/modems.
[Verizon Samsung Galaxy S III] mamill66:
Props & shout out to Whisk_33!!!! The Solution in the OP worked for me....Missed my damn texting!
[Verizon Samsung Galaxy S III] allride:
This worked for me!

Thank you Whisk_33
[Verizon Samsung Galaxy S III] mamill66:
Anybody try flashing a new nightly or verision after the fix? Not sure if I should press my luck or not.
[Verizon Samsung Galaxy S III] allride:
20120412-nightly stuck in bootloop when I tried this morning.
[Verizon Samsung Galaxy S III] Hybridnoob:
The OP didn't work for me (I followed the instructions perfectly multiple times and could never send more than one SMS after using the method from the OP), but I read through this entire thread and found a solution that did fix my problem. Sorry I'm not crediting who gave me the idea (I can't remember which member did for sure, but I think it was [MENTION=5791025]net-cat[/MENTION]). Here's what solved my SMS issue for two different Verizon S3's - please consider adding to OP as an option if plan A doesn't work:

1. Backup current ROM (CM11 in my case)

2. In Terminal Emulator - su reboot nvrestore

3. Battery pull once process completes, as it will bootloop

4. Boot into recovery, restore nandroid and flash MB1 firmware

5. Reboot system and profit. No SMS issues for at least 24hrs.

Side note - I had to manually wipe system, cache and dalvik and then install ROM and Gapps to get the next nightly to boot (CMUpdater bootlooped). Successive nightlies have installed and booted as expected. This was an easy and quick fix - I can't believe I didn't think to try this sooner. It's worth a shot if the OP method (much more time intensive) doesn't work or requires more effort than you're willing to put out.
[Verizon Samsung Galaxy S III] NMEAGENT:
What is nvrestore? Does it work on other ROMs as well like SlimKat?
[Verizon Samsung Galaxy S III] Whisk_33:
I may have too. I was one of the first people to get a working fix and I had to do the nv restore method... When I started hearing that people didn't need to use the SU route and were still getting results I figured it was a much better way. I thought the re-provisioning would have functioned the same way though...

I assume you had ALL and ONLY the symptoms described in the OP and that the sms was functional when you were in the root.66 TW rom?

I don't know enough to give you an accurate answer. you can see other posts on how to back up and restore the information, but from what I do know, it includes information related to the EFS which, at least in part, connects authorization/ID numbers to your service/physical phone and permits connection to the network.
[Verizon Samsung Galaxy S III] Whisk_33:
[MENTION=4911449]Hybridnoob[/MENTION]

You also might want to place a warning that people who go straight into an NV restore confirm that they have done a NV backup sometime in the past.

I saw that you thanked PerComp for his post in mastamoon's CM11 build http://xdaforums.com/showpost.php?p=51283750&postcount=768

I can't see how the OP didn't fix your phone but what you posted does... The OP includes every step you have and more to flush out any differences in peoples' setups....

any ideas?
[Verizon Samsung Galaxy S III] Hybridnoob:
Yes, good point about nvrestore.

The difference between the OP and the fix that worked for me (besides the amount of work and time) was the firmware I used. Ending up with MF1 firmware didn't fix my issue. Using older firmware was the key. The fact that I could fix my phone without Odin and reprovisioning is awesome. That's what I wanted to share.

I thanked PerComp for his efforts, but it didn't fix my issues. I hope this clears everything up and helps someone.
[Verizon Samsung Galaxy S III] Whisk_33:
Yeah there is definately something wrong with some of the GS3 and that MF1 firmware. I don't know why it is only happening to some people though.

(lol I never finished my thought about referencing that older post. oh well)

OP updated.
[Verizon Samsung Galaxy S III] Supercutetom:
I can only get a permanent fix if I remain on the stock firmware. It sucks but it works. Better than TouchWiz, though! I wish we could get someone who has extensive knowledge on the subject to help. I would love to know what's really going on here. It's such a strange issue with a wide variance in exactly who it effects, how it can be fixed, and what firmware works for some of us and what does not. If I had a newer phone I'd love to see if switching to it would allow me to continue with texts as well... But this ol' gal still has plenty of life in her now. I almost upgraded to the m8!
[Verizon Samsung Galaxy S III] mls21:
I've been following this thread - been having this problem for about a month or so. I got tired of constantly switching on/off airplane mode every time I wanted to send a text.

Anyway - I tried to do the long solution back on post 120, but was having some issues. I saw someone post that CleanROM worked fine, so I switched over to that. Good news - SMS is working. Bad news - it's based on TouchWiz, which is horrible.

I see you mentioned stock rom - what is that exactly? I assumed this was TouchWiz, but is it something else? And did you get it from this file: stock.vzw_root66.tar? I did download that - to get to this I assume I need to do it through Odin? Sorry for all the questions - I've rooted and flashed ROMs, but that's about the level of my (in)experience.

Another question - any other ROMs out there that would work with SMS? I was using CM v10 (hadn't upgraded to KitKat yet), but in playing around I did try Paranoid Android. I liked it, but SMS didn't work. I'm not tied to any - if there's another ROM out there that is not TouchWiz I'm willing to switch to that.

One last thought - I've done some research on apps that would just force everything to be MMS. Not the best solution, but a decent work around. Anyone know how to do this? I know - add a subject or attach a picture, but that's kind of a pain to do. I thought if there was a replacement app that will convert everything to MMS, that might be a decent workaround until this gets solved.
[Verizon Samsung Galaxy S III] Whisk_33:
Follow the steps listed in the OP.

The 'roo66.tar' file is the stock TW OS. I.e. If you load this and time travel to release date of GS3. Your phones will be identical.

Yes, you will need to use ODIN to use that file.

Any Touchwiz based ROM will have function SMS.

Making all your texts mms is an option, but I would imagine some of your messages won't be received as easily since most people will have to download the message before reading it. Try the method in the OP. If you have questions on the process, feel free to ask. I'm not an expert by any means, I only know what I did that worked for me.
[Verizon Samsung Galaxy S III] net-cat:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.

NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)

Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.

Requirements:

A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)

VRBMB1 AIO Flash, available here. (Thread here.)

I'm going to assume you know how to boot into and use recovery.

NOTE: Do NOT let the stock ROM install any updates.

Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)

Flash the VRBMB1 AIO.

Wipe data and cache.

Flash the stock ROM.

Boot into the stock ROM.

The reprovisioning seems to happen as a part of ROM's initial boot up.

Send a few text messages to test. (I sent them to Twitter.)

Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.

This would be a good time to back up your IMEI if you haven't already done so.

Reboot into your recovery, wipe data/cache and restore your nandroid backup.

At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.

DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!

CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
[Verizon Samsung Galaxy S III] NMEAGENT:
I thought that if we upgrade to 4.3 we wouldn't be able to flash a rom afterwards because of a locked bootloader. Also does this method wipe internal SD card?
[Verizon Samsung Galaxy S III] net-cat:
The ROM I linked isn't strictly a stock ROM. The person who built it basically took the stock ROM, rooted it and stripped out the locked bootloader. It's close enough to a stock ROM that it gets the job done. (To the point that it even "checks subscription status" when you enable tethering.)

Compare this to root66, which replaces the bootloader with the stock, locked bootloader. If you installed root66 and updated OTA, then yes. You would have a locked bootloader.
[Verizon Samsung Galaxy S III] NMEAGENT:
Oh OK thanks! And does this method wipe internal SD card?
[Verizon Samsung Galaxy S III] net-cat:
It doesn't seem to, but mine didn't have anything on it to begin with.

The main thing people were cautioning against for the 4.3 ROMs was that they seem to lack the code to do a factory reset that the 4.0 ROMs have, but that doesn't seem to be necessary.

Let me know if it worked for you.
[Verizon Samsung Galaxy S III] NMEAGENT:
I'll try to do it today but I might not get time. I'll definitely report back when I try it.
[Verizon Samsung Galaxy S III] mls21:
Thanks for this post! I'll give it a try tonight - seems much easier than the initial steps. If anyone else gets it working, can they post and let everyone know.

Quick question about this step, since I am a little bit of a novice with this stuff. Do I flash this just like I do a ROM? Meaning - boot into recovery and install this zip? If so - I do this, then immediately wipe data/cache while remaining in recovery?

Thanks again!
[Verizon Samsung Galaxy S III] mls21:
Well, I gave it a shot, and it seems to be working. I had an issue though - I booted into recovery, flashed the VRBMB1 AIO, wiped data/cache, but they got an error when I tried to install the stock rom. I was running CleanRom v8.1 from the same website/dev, so I just booted it back up anyway. Tried SMS (which was working since I was using a TouchWiz ROM), did the maps to get a lock on GPS, then went back to Paranoid Android ROM. So far so good on PA - I've sent lots of SMS and all went through. I'll update if I have any future problems, but flashing VRBMB1 AIO seems to do the trick...

Thanks again!
[Verizon Samsung Galaxy S III] NMEAGENT:
If I flash another AOSP ROM after doing this method, or the one in the OP, instead of restoring a backup will the fix still work?
[Verizon Samsung Galaxy S III] net-cat:
It should, but I haven't tested it.

There could be something during the initial startup sequence of some roms that could foul things up. Give it a try and post your results.
[Verizon Samsung Galaxy S III] NMEAGENT:
I'm thinking of trying it today. I'll report back when I do.
[Verizon Samsung Galaxy S III] NMEAGENT:
This worked like a charm! Im gonna try to see if the VRBMD3 or the VRBMF1 works with this method sometime soon.
[Verizon Samsung Galaxy S III] Whisk_33:
It sounds like I should update the OP then.

[MENTION=1726061]netcat[/MENTION] With the link you posted to a stock TW rom it removes the need for the user to use ODIN correct?

When I fixed mine I went back to the root.66 file and then just jumped back into CM11. I assume I am on an older modem. I'm guess that I should be able to simply flash the VRBMB1 AIO file now and everything should be functional still. agreed?

Perhaps you could help clear some confusion up for me. I thought that VRBMB1 AIO was a modem. I thought modem/radio are interchangeable in the case. Is there the MB1 the most current?

Where/when are we triggering this issue? Is it the firmware? I'm still stumped as to why this is only affecting some people and not everyone, but it seems like you have worked out the bare bones on what needs to be done. So good job.

and thanks to everyone who has been working on this. I'll update the OP later this weekend.
[Verizon Samsung Galaxy S III] Hybridnoob:
Based on my experience, I'm not convinced flashing to TW Is necessary. AIO is all in one and includes the firmware, modem, etc. MB1 is older, but the newest modem and firmware I haven't had problems with. MF1 firmware and newer modems (MF1 is the latest modem) have resulted in problems for both of my S3s. I never Odin'd or used TW to correct one of my phones. I only used the process I posted. Just trying to save some effort.
[Verizon Samsung Galaxy S III] Whisk_33:
I wonder if someone who has this problem only flashed the MB1 if that would fix it. For some reason I think [MENTION=2492427]PerCompLLC[/MENTION] tried that and it didn't work for him. That's why I had the longer version. Whatever fixes the problem in the least amount of steps for everyone is exactly what we are looking for. Saving effort is the name of the game.

I was on MF1 for months without it ever being an issue. and then suddenly in February the issues showed up. still very odd.
[Verizon Samsung Galaxy S III] Yabbakinz:
Okay. Just to add my two cents to help anyone out. I have been on 4.3 two stock since this issue happened and I have been looking for a fix like everyone else. I finally got the courage to go through with a fix, and literally all you have to do is flash the MB1 modem and then launch a TW stock ROM. It works fantastically after that with to my knowledge any ROM. So if you are looking for a fix, don't hesitate to try that.
[Verizon Samsung Galaxy S III] Whisk_33:
You flashed MB1, Flash TW, booted up, and then flashed/restored a CM11 Rom?

Can someone else verify that this is sufficient? That would be even easier than Netcat's
[Verizon Samsung Galaxy S III] Yabbakinz:
Possible "Fix" Found

Not completely correct but close. I had a 4.3 TW based rom for about 3 months as I searched for a fix myself and a finally stumbled upon net cat's fix and decided to see if i could tweak it a bit to make it easier. I launched into recovery and did not factory reset meaning I was still on 4.3 TW. I flashed the firmware suggested by net cat and then let the phone boot up normally. I then checked my settings and the new baseband was listed. I decided to factory reset and then flash the most recent CM 11 snapshot, which i believe in Feb. 17 ( funny enough right before the issue occurred), and the phone booted up fine and had texting working after the first sent. SUCCESS! I rebooted to see if it was a temporary fix and it was not. Texting worked fine and I had no issues jumping on LTE.

AS FAR AS I CAN TELL!!!

I have not tested phone calls or GPS specifically yet, but location services seem to be working in 4.4.2 and I assume that phone calls are okay and that would not suddenly become an additional issue.

The only difference between this method and Netcat's is that I was not already on an AOSP rom. His should still work fine if you are in his case. However if you have been stuck on 4.3 TW, it should be even easier. Good luck everyone.

EDIT: When reading over Net Cat's method i see that he says that the boot into TW is necessary after flashing the new baseband because the reprovisioning process is part of the rom's initial boot. I have no clue if this is true, but I assume that Net Cat's would not have said it without having good reason, so I am not sure it would be a good idea to boot straight into AOSP after flashing the firmware. Do not skip the TW 4.3 boot. I have no idea if that could brick your device or what but I would avoid it.
[Verizon Samsung Galaxy S III] NMEAGENT:
I doubt it would brick your device. It would just not fix the SMS issue. I'm pretty sure that the reprovisioning and flashing the MB1 AIO are the main parts of fixing this issue.
[Verizon Samsung Galaxy S III] Yabbakinz:
Oh okay. Just did not want someone to make that mistake and end up screwed.
[Nexus 5 Themes and Apps] LewisD94:
Hey guys,

Today I have been experimenting with the Nexus 5's boot animations and because I am a total newcomer to boot animations/graphics in general I wanted to share my journey with XDA, after all XDA is all about learning about our devices right?

So as I said, today I have been creating boot animations for the first time, please try not to judge my boot animations against the 'top of the range' ones as I am very new to this but either way I still wanted to share...

The first boot screen that I made today is called REVOLT:

REVOLT.zip - 1.03 MB (Flashable from recovery)

The second boot screen that I made today is called GoogleSimplicityWhite:

GoogleSimplicityWhite.zip - 628.53 KB (Flashable from recovery)

The third boot screen that I made today is called GoogleSimplicityBlack:

GoogleSimplicityBlack.zip - 590.52 KB (Flashable from recovery)

Note: If you need to revert back to your stock boot animation for any reason then I've provided a flashable zip for that too: GoogleStock.zip - 1.14 MB (Flashable from recovery)!

Thanks for taking your time to view my topic, I would greatly appreciate any feedback about these boot animations as I would like to start making better ones in the future...

Thanks to XDA Recognized Contributor @enricocid for introducing me to the flashable .ZIP template.

GoogleSimplicityWhite is being used in the following ROMs: PURE WHITE by @miseusegau​
[Nexus 5 Themes and Apps] blinde:
How about black version?
[Nexus 5 Themes and Apps] LewisD94:
Yeah, I could give it a go... I will change a few colours around later and come back with it for you! :)
[Nexus 5 Themes and Apps] EnricoD:
[MENTION=4808518]LewisD94[/MENTION]

I added Your boot (Nice job, I like it! :D) inside a flashable zip so You can remove instructions :P

View attachment 2594442

You can use the zip to flash Your works in the future :)

If You open the zip You will find an updater-script inside

Google_bootanimation.zip\META-INF\com\google\android\

It looks like this if You open on notepad++ :)

ui_print("[COLOR="Red"]Installing[/COLOR]");
ui_print("[COLOR="Red"]bootanimation[/COLOR]");
run_program("/sbin/mount", "/system");
package_extract_dir("system", "/system");
run_program("/sbin/umount", "/system");
ui_print("[COLOR="Red"]xda[/COLOR]");

You can change the ui_prints to visualize what You want during the flash process, just change the red hilighted text inside the quotes, and add what You want (the name of the boot, Your name etc etc)

and add the bootanimation.zip inside

Google_bootanimation.zip\system\media\

;)
[Nexus 5 Themes and Apps] LewisD94:
Glad you like it man!

I really appreciate your support! I'm going to release a few more tonight and this will come in handy, thanks!

:cool:
[Nexus 5 Themes and Apps] LewisD94:
Just updated the OP with the black version that you requested. :)
[Nexus 5 Themes and Apps] r0cky0790:
Will be following this thread.

"Cataclysm + ElementalX + Dalvik/Bionic Patches + Exposed + Gravity Box & Candy shop Mods + Jishnu's Camera Mod/LG G2 Camera Port + Latest GPU Drivers + -75 UV Across The Board + 4 OC Cores @ 2.226 GHz + TWRP" My Nexus Is The ?,┌П┐[◣_◢]┌П┐!
[Nexus 5 Themes and Apps] DivineDZN:
Tried all 3 :) Nice job they all look great when rescaled to fit my Galaxy SIII
[Nexus 5 Themes and Apps] yyz71:
Thanks Op nice job with the black one:good:
[Nexus 5 Themes and Apps] LewisD94:
Glad you like it dude! :cool:
[Nexus 5 Themes and Apps] miseusegau:
the most beautiful bootanimation of recent times .... include it in the next version of my stock .... great job lewis:cool:

Inviato dal mio Nexus 5
[Nexus 5 Themes and Apps] bmg1001:
I love the white one, unlike many others, I love white UIs, so this one just feels perfect. Thanks!
[Nexus 5 Themes and Apps] benkxda:
Thank you [MENTION=4808518]LewisD94[/MENTION] for you boot animations. Added to the Nexus 5 index :good:
[Nexus 5 Themes and Apps] LewisD94:
Brilliant, thanks for adding my boot animations to the index. Really appreciate that!

;)
[Nexus 5 Themes and Apps] justinisloco:
Those Google ones are just pure perfection. I haven't booted it up yet on my phone but I am really excited. I want to try both the white and black, and can't decide! They are just pure sex.

Thank you!!
[Nexus 5 Themes and Apps] LewisD94:
HaHa! I'm really glad that you like them, I'm so happy that my first ever boot animation attempts have been so well received by the XDA community! I'd be happy to see a reply from you to tell me which one that you ended up using out of the two...

Thanks for your feedback thus far,

LewisD94
[Nexus 5 Themes and Apps] justinisloco:
I ended up with the black one. I had the white one, and loved it, but with an all black boot loader screen, and all black phone, an all black screen was the way to go.

Just out of curiosity, this is showing my OCD, but could you make a black one that matches the boot screen with the padlock? That way it almost looks like the entire phone boot sequence is one seamless screen?

Like your black bootanim with that lock icon we get at the bottom