yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] dbow32:
Ok, I have gone through this with VZW for a week now. I've made 3 trips into the local VZW store and have about 6-7 conversations on the phone.

I had my sim card replaced and multiple factory resets. i finally caved in on Monday and let them send me a factory refurb. so after setting the new phone up last night and today and deferring the F'n update, I decided to go back into the VZW store and have them sit there while I accepted the update. I wanted them to see first hand that it wasn't in my mind and that there is something wrong with the OTA. So i proceeded to accept the update and when it was finished.. it started acting up again. One of the guys in there said take it back to the office and pull the battery/sim and let it set. then put it back...boot up and let it sit. Of course I followed his instructions and it did nothing. furious..... I called VZW and got tier one support. She quickly put me through to tier 2. I went through everything (for the 100th time) and we went through some setting (that I've done over and over). Finally, he found this statement "Verizon is aware of the update causing issues and is currently working on a solution". I wish the CEO of Verizon could go through what I've had to go through over the last week. he would be amazed at how departmentalized his company is. it shouldn't take that much to get to a resolution to a problem. You can call and talk to 1000 different tech's and they will all give you a different answer. I didn't want to trade in my original phone for a factory refurb. But I was desperate to fix the issue. I'm so pissed off right now I want to go back the VZW store and throw my phone and the window. I shouldn't have to pay for my phone until they come up with a fix.
[Verizon Samsung Galaxy S III] yepyep14u2know:
Stock rooted, flashed the aio zip file, completely removed the caller id app (in the system app folder) and running faster, smoother and LTE speeds back to normal. The battery life (zerolemon) is outstanding again. Haven't encountered any issues so far.
[Verizon Samsung Galaxy S III] sipock97:
Maybe have them try a new sim card.... Worked for chrisgriner.
[Verizon Samsung Galaxy S III] claymoses:
This is why I'm waiting to see what Scott can do with CleanROM... Definitely don't need the headache.
[Verizon Samsung Galaxy S III] DigitalMD:
Samsung / Verizon have OFFICIALLY now pulled the OTA and will release a fixed version later, That usually means 1 day for Samsung to fix it, and 3 months for Verizon to test and approve the release.

UNless you just enjoy fighting with Verizon and I do highly approve of that tactic, Just have them roll you back to to last good OTA, VRBMB1 and wait for a new update in 2 to 3 months. Or you can do it yourself with ODIN
[Verizon Samsung Galaxy S III] scottthreet32:
Been there done that I convinced vzw and now I have a note 2 I only spent money on they battery back cover pen and screen protectors and keep unlimited data

That update killed my phone I could not post anything

It screwed up data bluetooth that stupid hand poped up every time phone was restarted

Oh well wife was scared to update her s3 so now shes stick with it

The dam note 2 was too big for her hand anyways
[Verizon Samsung Galaxy S III] phoenixus:
Do we have a stock MB1 image anywhere? I only found LK3 in the QA forum
[Verizon Samsung Galaxy S III] jdk2:
Odin the LK3 and let the phone update to MB1.
[Verizon Samsung Galaxy S III] caifan:
I found MB1 Odin here http://samsung-updates.com/device/?id=SCH-I535
[Verizon Samsung Galaxy S III] phoenixus:
I thought you can't flash anything from that site?
[Verizon Samsung Galaxy S III] Addiso:
You Odin not flash
[Verizon Samsung Galaxy S III] caifan:
Dunno about that. I downloaded it but haven't flashed (Odin-ed) it.
[Verizon Samsung Galaxy S III] phoenixus:
Successfully ODIN'd back to BLK3, then took the update to MB1. It was odd because at first, my phone boot screen still showed the custom icon for recovery, but booted into stock recovery. After taking the MB1 OTA, this went away.

However, Verizon HAS NOT pulled the MD3 update. After updating to MB1, I was able to pull the MD3 update, but rejected it this time.

Staying on MB1 until they release a fixed version of MD3.
[Verizon Samsung Galaxy S III] Tiezane:
I pulled the battery, poor it back in, and booted up to get rid of that message on mine. According to some searching I did, it's common for that to come up as a false positive sometimes.

Sent from my Sega Master System via Carrier Pigeon.
[Verizon Samsung Galaxy S III] dohturdima:
Still on LK3, glad I was too lazy to update
[Verizon Samsung Galaxy S III] dumbstrong:
odin'd back to stock official mb1 from md3 last night and tried to see if my signal problem came from installation problems, but i guess vzw/samsung pulled the OTA update already

dropbox.com/sc/w96kuo7qqcnyh2y/6EkhFZ_LiQ
[Verizon Samsung Galaxy S III] rsswga:
I took the update then later got the de-odex one...3g and 4g sucked..would not send pic messages and failed text...

this morning I flashed the previous baseband...

works like a charm now
[Verizon Samsung Galaxy S III] robcop19:
great job on the odexed from bean

i actually used the odexed file because ive been wanting multiwindow soo bad and i didnt flash the fixed firmware package and i was finally able to flash my phone to metropcs with very fast data! ive got everything working on it and only after i updated with the MD3 update. and it works like a charm. ive had 0 issues so far and ive had it for a couple of day
[Verizon Samsung Galaxy S III] :
deleted
[Verizon Samsung Galaxy S III] jmz768:
Just downgraded to MB1 on my non-rooted device and everything is back to normal. I've never been one to tweak my phones so I was worried about messing something up, but it couldn't have been any easier. The harded part was waiting for the MB1 firmware to download.
[Verizon Samsung Galaxy S III] ricecake2000:
Its an adrenalime rush..... the waiting, and that first long boot! I am willing to bet you will start rooting and flashing :D
[Verizon Samsung Galaxy S III] Scrappy1:
After three years of Samsung phones, a clear pattern has emerged:

Phone is launched, most things kinda work, but some clear bugs and battery issues.

Major new Android version released, adding some features, but also adding new bugs and screwing performance in some areas. No reasonable testing could have possibly been performed. A turd was thrown over the fence.

Further updates arrive, fixing some things but adding even more bugs. Battery life is horrid, somewhere between 1/2 and 1/3 of life of an iPhone.

I can't stand such lack of testing and lack of robust programing. Samsung is horrible in software. I'm buying HTC One as soon as available on Verizon. Leaving Samsung and never looking back.
[Verizon Samsung Galaxy S III] hallstevenson:
The grass isn't always greener on the other side
[Verizon Samsung Galaxy S III] aarontsuru:
holy crap, I'm glad I missed this update.
[Verizon Samsung Galaxy S III] Scrappy1:
No, but the grass is rotting on this side. Couple examples recently.

I found out about USB on the go. Plug-in my external HD and cool, I could access file. Later in the day I find my battery almost dead due to extreme idle battery drain. I look at process usage and its a USB on the go related process that freaked out and kept processor awake.

I got new Samsung smart TV and tried Allshare Cast screen mirroring. Kinda worked but was laggy as hell. Then multiple times it said it became unstable and exited. Later that day my battery was dead again due to idle drain. Looking at process usage p2p_xxxx killed my processor, related to screen mirroring.

The list goes on and on for half baked Samsung features, buggy as hell, no respect for battery or runaway process usage. I want out from this bug infestation.
[Verizon Samsung Galaxy S III] carrevan:
FOR THE LOVE OF ALL THINGS HOLY... DO NOT UPDATE!!!!
[Verizon Samsung Galaxy S III] rand4ll:
Is there a download/odin file to flash just tge radios? I see all this all in one talk but no clear answer to this question. I will be rooting my gs3 tonight and going ober ti clean rom and sounds like I should flash/odin the mb1 radios while I'm at it.

Thanks in advance for any help.
[Verizon Samsung Galaxy S III] Quacker:
Does anyone know why we don't have a MB1 .tar file yet? I know I can just Odin back to LK3 and accept the OTA since the bad update was pulled, but I remember the LK3 .tar appearing very quickly.

I thought I was one of the lucky ones not having LTE issues, but after experiencing daily signal drops and awful battery life during my work commute, it's clear that I was wrong. Shame that we waited that long for multiwindow and now have to jump through hoops to remove the update.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
We do have a VRBMB1 tar, Open1your1eyes0 posted this in his No Wipe Jelly Bean Factory Images thread earlier this month. It's also on Samsung Updates under our device model.
[Verizon Samsung Galaxy S III] Quacker:
If you're just looking for the MB1 radio, check here, but if you already took the MB1 OTA update then it shouldn't be necessary.
[Verizon Samsung Galaxy S III] rand4ll:
Thanks. I took the md3 update and my phone acts wonky sending texts and mms. Sometimes a simple text takes over a minut to send...

I also found this page on same site.

http://invisiblek.org/sch-i535/modems/

Guesing I can juse use TWRP and install it since it isn't a tar file like odin usues? If so I will root/unlock, install twrp, flash clean rom and then flash these radios. Easy enough if that is correct.
[Verizon Samsung Galaxy S III] Quacker:
Thanks; I didn't see it listed in the sticky that includes the other tars, so I assumed it was still missing.

Yes, flash those files through recovery; don't use Odin. And yes, that would be the correct process, although you can flash the radio before or after the ROM.
[Verizon Samsung Galaxy S III] rand4ll:
Alright, ready to go, bt ran into another qestion. Do i flash the bootchain using bootlaoder option or the standard PDA option? It doesn't clarify in the guide and I don't want to mess it up. Phone is in odin mode and hooked up now, thanks for all the help!

EDIT: Watched video you use the PDA mode like i was guessing.
[Verizon Samsung Galaxy S III] Afro Samurai:
I understand your frustration but HTC is horrible about updating their software. They're going to tell you get a new phone before they update the phone's OS. Think before you leap.
[Verizon Samsung Galaxy S III] txkorm:
Spot on!

Currently not being productive on my S3.
[Verizon Samsung Galaxy S III] f308gt4:
How did you do it? I am stock, non rooted. Is there a step-by step instructions for downgrading to MB1?

Thanks!
[Verizon Samsung Galaxy S III] jmz768:
These are the instructions for how to install firmware.

http://droidviews.com/2012/how-to-install-android-4-1-1-jelly-bean-stock-firmware-on-galaxy-s3/

This is the firmware you need to install.

http://hotfile.com/dl/223791681/ff6...m-SCH-I535-VZW-I535VRBMB1-1360821900.zip.html
[Verizon Samsung Galaxy S III] allklrnoflr:
I have downloaded the firmware, How do I install it with a MAC?
[Verizon Samsung Galaxy S III] DigitalMD:
Samsung is without question, the best at keeping their phones updated with Android. If you don;t believe it, run on over to the HTC and Moto XDA threads. Now there is a problem though. If you are a Verizon customer, samsung is not responsible for final releases and deciding what features are in the ROMs you get from OTA, Verizon is , and Verizon adds a good 3 or 4 months for "extra testing" and verification prior to release of an OTA. And oh by the way decided which features go in and what is crippled or removed (Goggle wallet for example) . That's why Sprint S3's have more features and get updates sooner.
[Verizon Samsung Galaxy S III] kenhicg:
I just bought this from a friend and am on mb1. How do I get the update if none available are showing?
[Verizon Samsung Galaxy S III] rushless:
Uhhhh, thanks. Not! I already took the poison. Boo! I know you meant the person that posted ;)
[Verizon Samsung Galaxy S III] mehlord:
Md3 was causing me camera problems in liquid and carbon. Copied back to md1 no problems since.
[Verizon Samsung Galaxy S III] redwings8888:
Assuming I do this on a stock/unrooted, what implications does it hold pertaining to future OTA updates?

No issues?

Or do I have to manually odin future OTA as needed?

Thanks, these are probably super-n00b questions but curious and finding decent info searching online is no easy task...
[Verizon Samsung Galaxy S III] jmz768:
I'm not the one to answer that question, but I can't imagine there would be any issues.
[Verizon Samsung Galaxy S III] mehlord:
When I reverted back on my rooted phone, it was simply copying over via Odin and had 0 issues. However, I cannot speak to a nonrooted phone, as you can see, I am a noob.
[Verizon Samsung Galaxy S III] wijg:
You'll be perfectly fine. When Verizon releases new OTAs you'll still get them normally as if nothing ever happened. The only way you wouldn't is if you decided to root and altered system files, but if you stay unrooted then you have nothing to worry about. I even disable a bunch of the system apps and still get OTAs too.
[Verizon Samsung Galaxy S III] Pagaldesi4life:
Jmz768, since you're downgrading firmwares, when you installed the MB1 did you backup any data, files etc? Also in Recovery did you have to wipe data & cache partition as well?

I only ask because I found the downgrading firmware guide from the same site (http://droidviews.com/2013/how-to-downgrade-firmware-on-samsung-galaxy-devices/) and so was wondering if there were any issues from the method you used. I hope now since I prefer using your method as opposed to whats listed.
[Verizon Samsung Galaxy S III] jmz768:
I didn't backup anything and all of my pictures, files, contacts and everything else was still there. I also didn't do any of the other things you mention. According to the instructions, you only need to go into recovery and do a wipe if you're on a custom rom.
[Verizon Samsung Galaxy S III] bobAbooE:
Pulled

http://www.droid-life.com/2013/06/1...issues-is-working-with-samsung-on-a-solution/
[Verizon Samsung Galaxy S III] usmaak:
So my wife's phone is not rooted and she took the update. Since then, her phone has become pretty useless. Dead zones all over the place, and slow data when she has a connection.

Using Odin, it's possible for me to put her back to the prior version, even though she's not rooted? That would certainly be cool. I was trying to convince her to let me root her phone so that I could at least install an older radio and get rid of her signal issues. She's never let me root any of her phones, because she's afraid that she'll lose stuff and have to set up her phone all over again.
[Verizon Samsung Galaxy S III] Quacker:
If you're having 4G and battery issues on the new update (which I assume includes everyone that accepted the OTA) and you're at a loss for what to do, there's a couple of options.

You can use open1your1eyes0's no-wipe VRBMB1 factory image to return to the previous update while retaining all of your data on internal/external storage. This doesn't require root, but you have to use Odin.

Or, you can just flash the VRBMB1 firmware. This fixes the data/battery issues on the new baseband while retaining the other components of the update like multiwindow. This requires a rooting method so that you can unlock the bootloader and install a custom recovery. Then, simply install the VRBMB1 firmware through recovery.
[Verizon Samsung Galaxy S III] redwings8888:
I down-graded my unrooted stock from MD3 back to MB1. No issues what so ever. Fixed the horrible radio, and lost no data, as expected.

My Verizon rage went down slightly since my phone is working normally.

Edit: I used ODIN and followed instructions posted by jmz768 in this thread. Thanks to everyone here on xda helping fix the mess Verizon dropped on us yet again...

By far the biggest pain in the rear on this simple process was waiting....waiting....and more impatient waiting for the horribly slow file host to download the 700+ mb MB1 firmware lol
[Verizon Samsung Galaxy S III] sipock97:
Just wanted to say thanks to this forum and all the contributors that have helped with this Verizon debacle. While my wife's phone did not have an issue with the ota, it is a relief knowing that real help is only a post away. Great job everyone! :thumbup:
[Verizon Samsung Galaxy S III] allklrnoflr:
Very cool, Was able to downgrade no problem....No updates available either so I'm glad I don't have to worry about the bad upgrade anymore.
[Verizon Samsung Galaxy S III] txkorm:
So I get a call from Verizon tech support from my initial conversation and they left me a voice mail to call them back. So I did which required the usual 5 minutes of button pushing and transfers only to find out that they called me to see if my phone was working. I asked them if they did anything and they said no.... So how the hell is my phone working?! What I found out on the call is that we are in "critical status" meaning this is Verizon number one priority...... And it will be fixed very soon... Blah blah blah blah blah. I was unable to get a refund or a new and different phone after 30 minutes of worthless banter. He did offer to get me a new phone if I opened another line.... I really hate Verizon! He did guarantee me that it wouldn't be two months before the issue would be resolved. I advised him to be careful what he says.

Currently not being productive on my S3.
[Verizon Samsung Galaxy S III] f308gt4:
Thank You Again! I finally had time to do it this evening. My phone is back to normal!!!

THANKS!!!
[Verizon Samsung Galaxy S III] Pagaldesi4life:
Does anyone happen to know the MD5 info for the zip?? My connection had a hiccup and I want to make sure its correct before I update my phone. Thanks!
[Verizon Samsung Galaxy S III] scorchedsky:
Is anyone running MB1 modem AND rpm, with the rest of the firmware being MD3 (trust zone, bootchain)? I'm running just the MB1 modem now, with RPM/TZ/BC all MD3 versions...the 4G->3G handoffs are definitely better, but I still feel like it's not quite where MB1 was beforehand. Would flashing the MB1 RPM help with anything?
[Verizon Samsung Galaxy S III] david_hume:
Lol, I'm STILL running the MK1 modem and RPM. Best combo I've ever used compared to the newer modems.
[Verizon Samsung Galaxy S III] miniwarlord:
Wow. I feel like I just hit the lottery. MD3 is working fine for me. The only issue I have is waiting for my ROM dev to update for the Base. I did not choose to take the OTA, I had my phone replaced and the update came with the the one.

BTW... Samsung builds the HW feature set. Verizon does the updates. A different phone will not change that.
[Verizon Samsung Galaxy S III] detonation:
That's Verizon's customer service line for ya...a secondary sales line.
[Verizon Samsung Galaxy S III] hfd2049:
My new phone is out for delivery. Complain enough and the update and get what you want!
[Verizon Samsung Galaxy S III] ricecake2000:
What phone did you get?
[Verizon Samsung Galaxy S III] hfd2049:
The same. They wouldn't let me upgrade because nothing is wrong with the phone before the over the air upgrade.

---------- Post added at 07:30 PM ---------- Previous post was at 07:27 PM ----------

Now since I'm UN rooted I have to go through the painstakingly long process of rebuilding my new phone here. See you in a couple hours.
[Verizon Samsung Galaxy S III] usmaak:
New or refurbished? I guess you won't know that until you actually get the phone.
[Verizon Samsung Galaxy S III] ricecake2000:
Probably a refurb , but who knows since the new s4 is out. I paid off contract for my new device but ever since I took the ota it sucked. That's after Odin back to vrblk! I think it permanently breaks the phone!
[Verizon Samsung Galaxy S III] usmaak:
Wow. I hope it doesn't permanently break the phone. My wife took the update and is anxiously waiting for a fix. I have heard of people who flashed an earlier radio and fixed the signal problems.
[Verizon Samsung Galaxy S III] telveer:
The phone is not broken. In fact, even the update is not broken except for the radio part. As long as you can put back MB1 radio after the update, you should be OK running the rest of the MD3 OTA, which includes "premium" features like multi-window but also includes bloatware like CallerID (which can be disabled). The best news is that you can do all of this without root.

If you ask for a replacement phone, you will get one with MB1 Radio and ROM (without "premium" features) - thats the only official way to get your phone fixed if it has MD3 issues. VZW pulled MD3 update out so you will not get the udpate anymore.
[Verizon Samsung Galaxy S III] usmaak:
How do you replace the radio without rooting? I told my wife that she had two choices. I could take her back to MB1 with the no wipe version, or I could root her phone and go back to the prior radio.

Man, these phones are so different from my old Evo. Couldn't do anything to that without root.
[Verizon Samsung Galaxy S III] hfd2049:
Refurb phone. Up and running with no issues. I consider myself lucky because I'm way out of warranty on my old phone and they have me this Refurb for nothing. Almost done setting it back up.
[Verizon Samsung Galaxy S III] rushless:
I disagree that it is just the radio. Even Verizon techs will tell you that. The bloat is part of the issue as well. Of course, they say some portions of the update are "broken". My device runs smoother and less junk running in the background. Worthless update, including the radio.
[Verizon Samsung Galaxy S III] rsswga:
if ur having issues after u updated to the crappy radio, call verizon and they'll send u a replacement phone..mine will be here monday..
[Verizon Samsung Galaxy S III] sipock97:
Got lucky with my wife's phone as it did not have an issue, but if it did, I would have just rooted it and flashed back to MB1. Would be quicker, without the wait, and you keep your phone.
[Verizon Samsung Galaxy S III] DigitalMD:
Verizon techs would be just about the last people I would take advice from. Their usual advice is pull battery, reboot, then wipe phone reboot , then buy a new phone.

Applications sitting on your phone unused have no impact on performance. Not that I am a fan of Verizon's almost always useless applications, but one man;s bloat is anothers useful app.,Occasionally an app goes rogue when it can't get data or GPS (this can happen on any ROM, some apps are just poorly written), but if you never used it, its inactive and doing nothing in almost every case with modern android devices, (not Foryo and such) the idea that removing extra apps jumps your performance is a placebo.If it makes you feel better and you are rooted, you can always freeze the apps you don;t like and they disappear.
[Verizon Samsung Galaxy S III] rsswga:
yea I can't believe they sending me another one, such a 30 second fix... this is number 4..
[Verizon Samsung Galaxy S III] eman3316@optonline.net:
Here is an idea Samsung. Instead of taking the time to fix a now outdated OS, how about just taking the time to work on 4.2.2!

You think if these companies would learn or take away anything thing from Apple it would be to give the people updates to the latest OS! I cannot wait to get back into a Nexus device again if Crapizon every allows another one on their network.
[Verizon Samsung Galaxy S III] Hack150:
There are plenty of 4.2.2 AOSP ROM's out there that will make your S3 just like a gnex if that is what you want.

As for this problem, simply flash back to the MB1 modem and freeze/remove the new caller ID app.
[Verizon Samsung Galaxy S III] eman3316@optonline.net:
I need a stable fully working device and if things are still like they were with AOSP roms on this phone the last time I checked then I works not call that stable. Has all the prior bugs been worked out? Last time I checked was probably like 3 months ago but back then people claimed everything worked great that was sure not the case.

I have been so dedicated to purchasing an HDTV these last few months all my tech attention went there and I have just been out of the loop with my S3. I have been all about avs forum lately.