Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Original Official carrier file?

TMar said:
You are correct about every thing except for the broken firmware. There's nothing wrong with 3.1.
Click to expand...

Except for the hundreds (probably thousands) of people who've experience locked phones that appear to be in a coma for several minutes at a time. Some people have had these lockups multiple times a day since upgrading to 3.1.

Don't make naive statements like that just because YOU haven't personally experienced the problem. Lots of people have and there are plenty of threads here and on Apple's own discussion forums about the issues. I rolled back to 3.0.1 in order to have a "usable" phone again.
 
jkozlow3 said:
Except for the hundreds (probably thousands) of people who've experience locked phones that appear to be in a coma for several minutes at a time. Some people have had these lockups multiple times a day.

Don't make naive statements like that just because YOU haven't personally experienced the problem. Lots of people have and there are plenty of threads here and on Apple's own discussion forums about the issues.
Click to expand...

Wow hundreds (possibly thousands) out of how many millions (by the way I would like to see some statistical data to back that up) ? I have personally updated 6 phone with no problems. So before you make naive statements with statistics pull from you ***, think twice.
 
I just manually updated a 3.0.1 3G to 5.5 carrier file and it worked beautifully, tested from a 3.1 GS with 5.5

Did it on a Windows based PC:

Run "C:\Program Files\iTunes\iTunes.exe" /setPrefInt carrier-testing 1 [/I] from command line with iTunes closed, then start iTunes

Open iTunes -> Shift-click Update -> Change file type to Carrier File -> Select carrier file -> Enjoy

Terminal command for Mac is: defaults write com.apple.iTunes carrier-testing -bool TRUE
 

Attachments

  • ATT_US.zip
    20 KB · Views: 114
TMar said:
Wow hundreds (possibly thousands) out of how many millions (by the way I would like to see some statistical data to back that up) ? I have personally updated 6 phone with no problems. So before you make naive statements with statistics pull from you ***, think twice.
Click to expand...

there's something clearly wrong with 3.1. just cause you're not experiencing the issue doesn't mean there's not. i'm one of the users that experienced the "coma" from 3.1. it flippin sucks. i've done DFU restore and the issue came back.
 
Dakk said:
I just manually updated a 3.0.1 3G to 5.5 carrier file and it worked beautifully, tested from a 3.1 GS with 5.5

Did it on a Windows based PC: Open iTunes -> Shift-click Update -> Change file type to Carrier File -> Select carrier file -> Enjoy
Click to expand...

where did u get the carrier file?

edit: nm didn't see attachment
 
Dakk said:
I just manually updated a 3.0.1 3G to 5.5 carrier file and it worked beautifully, tested from a 3.1 GS with 5.5

Did it on a Windows based PC: Open iTunes -> Shift-click Update -> Change file type to Carrier File -> Select carrier file -> Enjoy
Click to expand...

Is this ok to put on a 3G with 3.0?
 
trunksu said:
there's something clearly wrong with 3.1. just cause you're not experiencing the issue doesn't mean there's not. i'm one of the users that experienced the "coma" from 3.1. it flippin sucks. i've done DFU restore and the issue came back.
Click to expand...

If there's was "clearly" something wrong wouldn't everyone be experiencing it?
 
TMar said:
Wow hundreds (possibly thousands) out of how many millions (by the way I would like to see some statistical data to back that up) ? I have personally updated 6 phone with no problems. So before you make naive statements with statistics pull from you ***, think twice.
Click to expand...

Count the number of affected people in this thread alone and there are hundreds affected. Given the fact that a large percentage of the population doesn't regularly post on forums and wouldn't even know where to look to find a forum to post their problems, you can probably extrapolate the "hundreds" of affected users to a number that is easily in the thousands.

http://discussions.apple.com/thread.jspa?threadID=2152619


Don't accuse me of pulling numbers out of my @#$. I have been following the threads on 3.1 problems very closely because I was unfortunately one of the affected users. I know several people that are NOT affected, but I personally know a couple that have had the comas along with myself. Maybe there was a minor hardware revision along the way that's leading to an incompatibility with a small percentage of phones. I have no idea, but I've restored and reinstalled 3.1 as a "new phone" and still had the lockups (although not as frequently as some posters) and eventually rolled back to 3.0.1 to get a working phone.

Please don't be rude just because you've had good luck with 6 phones. I wish that were the case with me, but it's not. Like I said, 3 of my iPhone friends (out of over a dozen) have had the issues and so far no one in any of those threads has found a workaround that works for more than a day or two. Multiple people have restored as new phones, disabled push notifications, etc to no avail.

I'm not trying to argue, but just because not every person who bought a Ford Explorer with Bridgestone (or was it Firestone?) tires had tire failure doesn't mean there wasn't a known issue! Known issues typically only affect a small percentage of users historically speaking. That doesn't make them NON-issues.
 
TMar said:
If there's was "clearly" something wrong wouldn't everyone be experiencing it?
Click to expand...

so let me get this straight. just because not everyone experiences the issue, then 3.1 is perfect? fine if you think 3.1 is perfect, by all means it is.
 
nabechu said:
got it working on my jailbroken 3gs :cool:
Click to expand...

HOW?! I still can’t get it to do anything! :( I’ve got the 5.5 carrier file and i don’t even have the “MMS: On/Off” option or any of the previous options i had with the hacked 5.1 file.. wtf!
 
jkozlow3 said:
Count the number of affected people in this thread alone and there are hundreds affected. Given the fact that a large percentage of the population doesn't regularly post on forums and wouldn't even know where to look to find a forum to post their problems, you can probably extrapolate the "hundreds" of affected users to a number that is easily in the thousands.

http://discussions.apple.com/thread.jspa?threadID=2152619
Click to expand...

That's like going to a doctors office to poll for sick people and then assuming there's an epidemic because everyone there is sick.

jkozlow3 said:
Don't accuse me of pulling numbers out of my @#$. I have been following the threads on 3.1 problems very closely because I was unfortunately one of the affected users. I know several people that are NOT affected, but I personally know a couple that have had the comas along with myself. Maybe there was a minor hardware revision along the way that's leading to an incompatibility with a small percentage of phones. I have no idea, but I've restored and reinstalled 3.1 as a "new phone" and still had the lockups (although not as frequently as some posters) and eventually rolled back to 3.0.1 to get a working phone.

Please don't be rude just because you've had good luck with 6 phones. I wish that were the case with me, but it's not. Like I said, 3 of my iPhone friends (out of over a dozen) have had the issues and so far no one in any of those threads has found a workaround that works for more than a day or two. Multiple people have restored as new phones, disabled push notifications, etc to no avail.

I'm not trying to argue, but just because not every person who bought a Ford Explorer with Bridgestone tires had tire failure doesn't mean there wasn't a known issue! Known issues typically only affect a small percentage of users historically speaking. That doesn't make them NON-issues.
Click to expand...

You did pull those numbers out of thin air unless you counted them all yourself. You said thousands, so how many 6000? A very small fraction of a percent of all phones sold. You need at least 600,000 to even get up to 1%.

Do you think it's a smart thing to compare public safety (peoples lives) statistics with people having a few problems with their phones?
 
TMar said:
That's like going to a doctors office to poll for sick people and then assuming there's an epidemic because everyone there is sick.



You did pull those numbers out of thin air unless you counted them all yourself. You said thousands, so how many 6000? A very small fraction of a percent of all phones sold. You need at least 600,000 to even get up to 1%.

Do you think it's a smart thing to compare public safety (peoples lives) statistics with people having a few problems with their phones?
Click to expand...


I didn't say it was life-threatening or a public safety issue. Nor did I say it was affecting more than 1% of users. What I did say is that it is affecting SOME users. I'm not sure why you're being so argumentative. Some unfortunate people are having problems. Are you an Apple executive or something? WTF?

Anyway, I'm done discussing this.
 
Dakk said:
I just manually updated a 3.0.1 3G to 5.5 carrier file and it worked beautifully, tested from a 3.1 GS with 5.5

Did it on a Windows based PC: Open iTunes -> Shift-click Update -> Change file type to Carrier File -> Select carrier file -> Enjoy

You might need to enable the manual update: Run "C:\Program Files (x86)\iTunes\iTunes.exe" /setPrefInt carrier-testing 1 from command line with iTunes closed, then start iTunes
Click to expand...


Thanks! I had to run the cmd from a command line and then it worked perfectly with 3.0.1!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back