Comments on: Mystery Solved: AT&T Carrier File Update 5.6 for iPhone Did What Exactly?

By: asraa

asraa — Sat, 24 Apr 2010 05:49:06 +0000

if i get this Carrier : AT&T 5.6 will i still be able to unlock my phone???

By: Joe

Joe — Sat, 23 Jan 2010 18:07:31 +0000

they dont allow tethering because the iphone doesn't compress data like crapberry's do. They have enough trouble keeping data to the iphones already, the last thing they want is a computer hogging all the data too!

By: ebatti

ebatti — Tue, 03 Nov 2009 02:24:03 +0000

AT&T is abusive of the iPhone customer. Blackberry devices have tethering, and can stream video via Sling Player over 3G. Send these jokers a complaint. See http://www.lionfishpictures.com/2009/11/i-have-had-it-with-at.html for a very well written complaint letter. Feel free to copy it and send it to them.

By: Steve Niedzwiecki

Steve Niedzwiecki — Mon, 02 Nov 2009 19:00:53 +0000

I have that problem with 5.6. I didn't have 5.5 so this was my first MMS update.

By: jes

jes — Fri, 30 Oct 2009 22:30:27 +0000

Hi i am experiencing the same problem unable to send/receive mms. Everything was working fine after the release of 5.5 however last night it stopped working. I then tried updating to 5.6 however still no luck. Called Apple support and ATT went through the usual. reset network, switch to edge, even some 5005.... nothing. I tried the sim card in my n97 and was able to send and receive mms on that phone. Can anyone tell me what I can try?? thank you

By: Joe Mamma

Joe Mamma — Thu, 29 Oct 2009 15:34:29 +0000

If you are having issues with MMS on the Iphone contact AT&T and tell then to update your inei in both of their systems. That should fix the issue. Also go into Settings>General>Profile>and remove the profiles.

By: Dradis

Dradis — Wed, 28 Oct 2009 04:13:44 +0000

John says, "Resetting my Network settings to default fixed it immediately though, before the update was released."

Just wanted to confirm this. I am using 5.5 settings on a jailbroken and unlocked phone w/ 3.1.2 fw. I am using BossPrefs to block Edge/3g, so after resetting the network settings I went back to BossPrefs and turned off Edge/3G. MMS still works, even w/ these turned off.

Also, just as a word of advise, when you say things like "I’m still using 5.0 settings." follow that up with "...and it works for me" or "...and nothing works". I dont care what version you're running if i dont know what you can/can't do.

By: matucon312

matucon312 — Sat, 24 Oct 2009 15:55:24 +0000

I'm on 5.5; haven't had this issue since MMS was officially "turned on" on AT&T's end. Oh, and I do have tethering with 5.5.

By: Skillzdatkillz72

Skillzdatkillz72 — Sat, 17 Oct 2009 01:18:48 +0000

Funny thing is never had a problem before with 5.5 but now with update 5.6 I get red exclamation

By: lightnin

lightnin — Fri, 16 Oct 2009 19:00:38 +0000

anyone having a problem with mail over 3G network since the update?

By: divinIN

divinIN — Thu, 15 Oct 2009 17:37:42 +0000

Still have the problem. /golfclap

By: Kevin Benore

Kevin Benore — Thu, 15 Oct 2009 08:28:41 +0000

Still having the issue after the update. maybe a system restore will help?

By: Larry

Larry — Wed, 14 Oct 2009 22:16:32 +0000

I absolutely had the bug and it drove me nuts. I didn't reallize the carrier update was what fixed it, but it's definitely gone now. Wahoo!

By: Gregory Foster

Gregory Foster — Wed, 14 Oct 2009 19:51:35 +0000

Didn't have that problem.

By: Brian

Brian — Wed, 14 Oct 2009 19:51:17 +0000

It still takes hours for mms messages to come/go through

By: Corrina

Corrina — Wed, 14 Oct 2009 19:20:31 +0000

I did have that problem and it does seem to be fixed now. I wasn't sure, either what that update did so thanks for clearing it up.

By: nick

nick — Wed, 14 Oct 2009 18:41:24 +0000

yes nostbdeff fix the problem for me .... after dl the first mms update the red ! thing would pop up .....the sending bar still lags but get the job done as it sends the image if u have seevice

By: The67beast

The67beast — Wed, 14 Oct 2009 18:20:24 +0000

First! Jk. I never had the issue.

By: Doc

Doc — Wed, 14 Oct 2009 18:08:47 +0000

Seems to have fixed it.

By: Gibeath Haaraloth

Gibeath Haaraloth — Wed, 14 Oct 2009 17:31:53 +0000

I had the red (!) for every other SMS I would send on 3G. Downgrading to EDGE allowed messages to be sent. Having just upgraded from my original iPhone to the 3GS left me wanting in some areas.

By: Bryce

Bryce — Wed, 14 Oct 2009 17:25:17 +0000

I had this issue before 3.1.2, but even after the carrier update, nothing changed. In fact, it seems that I'm having MORE trouble with those pesky little exclamation marks than I have been before.

By: Bill Taroli

Bill Taroli — Wed, 14 Oct 2009 17:12:40 +0000

I didn't experience that failure before, but have seen it twice on 5.6 carrier file.

By: Glenn_VA

Glenn_VA — Wed, 14 Oct 2009 16:04:19 +0000

I guess I lucked out. I didn't experience this problem with 5.5. I applied 5.6 and it now seems the status bar goes much quicker.

By: t-ditty

t-ditty — Wed, 14 Oct 2009 15:48:50 +0000

i jailbroke my phone yesterday.....i was wondering if i install it, if it will break my jailbreak....anybody know?

By: Iphone4idiots

Iphone4idiots — Wed, 14 Oct 2009 15:28:20 +0000

I had that til Stealth had me call ATT. MMS wasn't working cause they had me as a 2G. I jailbroke to 3.1.2 yesterday but left carrier at 5.5. No need to update as far as I can see.

By: Mondozer

Mondozer — Wed, 14 Oct 2009 15:28:05 +0000

Didn’t fix the problem for me.

By: Dan

Dan — Wed, 14 Oct 2009 15:22:40 +0000

I had that issue before the update, where it would occasionally fail to send an MMS. However, NOW I've noticed a problem where I can't send an MMS at all while I'm on a call... I'm SURE this worked before (maybe I'm wrong..?) I can send a txt, but not MMS, while on a call. Does anyone else have this problem? The MMS fails almost immediately, then I get the red (!).

By: Andy

Andy — Wed, 14 Oct 2009 15:16:46 +0000

First! Indint see the difference between 5.5 and 5.6 really. I didn't have that bug

By: Nuzzi

Nuzzi — Wed, 14 Oct 2009 14:57:03 +0000

I have this problem. Had it from day one and still have it after this update. I am working with Apple tech support now, but we haven't had any luck.

By: r3k

r3k — Wed, 14 Oct 2009 14:42:44 +0000

I had the problem for several days once it went live. I worked with tech support and they were able to fix it within a couple of minutes.

By: BSmith4832

BSmith4832 — Wed, 14 Oct 2009 14:29:28 +0000

@ Mr. Wu - did you do the manual IPCC update via iTunes with the hacked carrier file?

The (first) hacked carrier file had a ton of issues with Visual Voicemail. AT&T thinks they are having a huge VVM crisis for the last month and a half - when in reality, they don't have an issue (well, besides obvious AT&T issues) they have a ton of people that tried the hacked carrier file and in turn called AT&T to let them know their VVM had an issue. AT&T did everything they could do and can't "figure it out".

One of my guesses would be that AT&T is "thinking" their fixing a possible issue with VVM and maybe added it into this carrier file. I'm just guessing here. I was told from an AT&T tech (and friend) that they have been running crazy (since that hacked IPCC file launched) trying to fix VVM issues.

Regardless, try resetting your network settings on your phone. This usually works for most voicemail related issues.

By: dagwolf

dagwolf — Wed, 14 Oct 2009 14:25:47 +0000

I don't know if it's a "problem". I'm still running carrier 5.0 on a jailbreaked 3G at 3.0.1. The progress bar does stall at around 90% with MMS for about 2 seconds, but then it sends just fine. Like keeping the 5.0 because it still has the tethering options.

By: jglowe74

jglowe74 — Wed, 14 Oct 2009 14:21:34 +0000

actually, yes. this fixed the red exclamation problem for me. i couldn't send MMS until now. so...THANKS!

By: BSmith4832

BSmith4832 — Wed, 14 Oct 2009 14:21:05 +0000

@ Mark Bergman - do you need your iPhone unlocked (are you on a different carrier)? If not, blackra1n is out and can Jailbreak 3.1.2 incredibly easy, I did it last night.

If you run a script (search for the walkthrough to enable MMS on 3.0) on your PC it will allow you to select IPCC files in iTunes (Shift+Click on Restore). Then you might be able to download the IPCC file from somewhere on the internet and manually update that way. However, I'm not sure if the IPCC file has a prerequisite such as having to be on 3.1.2 in order to install on the phone.

I was originally hesitant to upgrade because I didn't want the new baseband (unlockable, as of now). However, after thinking it over I have no need to unlock so I simply upgraded my iPhone to 3.1.2, restored from a recent backup, ran blackra1n, done. Jailbroke in less than 30 seconds. I'm using a 3GS.

By: Jon

Jon — Wed, 14 Oct 2009 14:12:11 +0000

Had that problem the reset the network settings on the iPhone and it went away.

By: Mark Bergman

Mark Bergman — Wed, 14 Oct 2009 14:09:47 +0000

Is there a way to get the carrier file update without updating the OS? I'm not getting a prompt for the carrier file. My 3GS is jailbroken so I'm not ready for the update to 3.1.2 yet.

By: ibetts

ibetts — Wed, 14 Oct 2009 14:08:37 +0000

I had this issue when MMS was announced. After several failed MMS messages over two days, I called AT&T. They said that some special system still showed my phone as edge instead of 3G. It took them about 3-4 days to finally get that system to open, and change my setting at the network side of things. Then my messages worked. Don't know if this upgrade would have fixed it, but the problem matches what I had.

By: Mr Wu

Mr Wu — Wed, 14 Oct 2009 14:08:33 +0000

Anyone hanging on to the 3.0 for tethering reasons having a voicemail problem since this latest update? My voicemail suddenly takes 30 mins to an hour to get to my iPhone 3Gs. Never had a problem before they released the update. Are they secretly forcing us to update by screwing with voicemail? CONSPIRACY??!!

By: BSmith4832

BSmith4832 — Wed, 14 Oct 2009 14:06:07 +0000

I've been having that problem in one certain area that I go to. I can always send texts, browse internet, etc etc although I could not send an MMS. I'll be there again on Saturday - I'll give it a try then. (P.S. I have a solid 3G connection in that area)

By: John

John — Wed, 14 Oct 2009 14:05:27 +0000

I was having this problem on every MMS sent before the 5.6 update. Resetting my Network settings to default fixed it immediately though, before the update was released.

By: Msousa

Msousa — Wed, 14 Oct 2009 14:02:13 +0000

I'm still using 5.0 settings.

By: ScaliasPhone

ScaliasPhone — Wed, 14 Oct 2009 13:59:53 +0000

I had that problem for the about the first 8 hours after receiving the ability send MMS. It went away on it's own. I just assumed it was carrier traffic.

By: Bryan

Bryan — Wed, 14 Oct 2009 13:56:10 +0000

I was having that issue before and after, but with texting... Not MMS

By: O Boogz

O Boogz — Wed, 14 Oct 2009 13:54:24 +0000

oh btw i currently own a 3G S

By: O Boogz

O Boogz — Wed, 14 Oct 2009 13:53:51 +0000

i was told by by an Apple support rep that the reason i was receiving this error was because i didnt have the correct messaging plan. i had the 2g plan which bundled internet & messaging for $30. For the 3G & 3G S you needed to have the separate internet & messaging plan in order to use MMS. After that it worked fine.

By: Steve

Steve — Wed, 14 Oct 2009 13:53:07 +0000

Using carrier files 5.5 and 6. Both get that message sometimes even with standard SMS.

By: firesign

firesign — Wed, 14 Oct 2009 13:47:36 +0000

i had that problem when mms was first released but it seemed to clear before this update. glad they fixed it though.

By: Benny P

Benny P — Wed, 14 Oct 2009 13:47:16 +0000

Ditto. Happened to me twice this weekend. Better get home and patch up. Yo

By: aimz

aimz — Wed, 14 Oct 2009 13:46:34 +0000

I've had that problem both before and after this "bug fix".

By: Joe McG

Joe McG — Wed, 14 Oct 2009 13:39:19 +0000

I definitely saw this before the MMS release, but once it was out, it worked fine. I did see alot of people complaining about this problem though.