Since RIM and Sprint suck and can't do their damn job, I'll do it for them.

1. Download the Telus OS
2. Download the Nextel OS
3. Install both of them onto your computer
4. Replace the phone.alx file and the phone.cod files on the Nextel Operating System with those from the Telus Operating System.
5. Delete the vendor.xml file
6. Remove the Telus OS from your computer
7. Open Desktop Manager
8. Go to the application loader
9. Click through and choose to downgrade the Operating System.

I have done this on 8 8350i's that were having echo issues and had been told to "remove the skin or case".

All 8 of the Curves are not echoing now.

RIM and Sprint, I would like my "We Suck And You Did Our Job For Us" bonus sent to me in small, non-consecutive American Currency.

If need be, I can create a "visual" walk-through of how to do what I wrote above, but those of you who have "hacked around" on your OS before should know exactly what I am talking about.

LMAO at "reported on a limited subset of devices".

If Pinocchio worked for Sprint, his nose would have just stretched from Kansas City to Los Angeles with that lie.

And I love the "Work arounds". LMAO. Use speaker phone or the wired headset.

How about "No. Give me a damn credit on my bill".

That's a real shotty answer that's like like saying we forgot to include the "phone" portion of your blackberry but it's ok, you can just email, BBM or IM them instead.

That is truly an unacceptable recommended solution to the given problem.

"Your phone doesn't work? So use this extra stuff to work around it. Sorry Bud, Your SOL."

That wouldn't cut it for me.

HAHAHAHAH, Sprint customers should be able to go back and swap device for known defect no matter if it's past the 30 days or not.

Here you go Nextel Peeps:
http://www.blackberryhomepage.com/blogger/2009/02/19/exclusive-how-to-fi...

Hrm...Didn't take the whole link...

http://www.blackberryhomepage.com/blogger/2009/02/19/
exclusive-how-to-fix-8350i-nextel-curve-echo-issue/

actually sprint and rim DONT suck- in fact i work for Sprint advanced technical support and everytime someone has an echo on thier phone it's because the volume on it is up so high that the speaker is picking it up

This is nextel's best phone by far-

It's not the microphone picking up the speaker because someone is talking too loud. It's typical BS responses like that that makes the Sprint BlackBerry Support team the laughing stock of the US carriers.

What RIM and Sprint haven't been able to accomplish since this device launched I was able to accomplish in a matter of less than an hour just by using some common sense and trial and error.

The issue is that the person who is talking on the OTHER end of the 8350i (not the user) is experiencing the echo issue when THEY speak...So please old wise one...explain how "the earpiece volume is up so high that the microphone is picking it up" is possibly causing the echo. If that were the case, Sprint would be advising to NOT use the speakerphone, and it would be echoing background noise on the 8350i end of the conversation.

Of course, the NDS reps are probably on these forums and will see this, realize that it fixes the issue, then send an email out to the regional reps claiming that they figured out a fix @ Sprint Campus in Kansas City, just like they did with the "skin is causing the echo" email that they sent out a week ago.

They pretty much copied the post HERE ON CRACKBERRY WORD FOR WORD and then tried to play it off in the email as "one of our senior tech support reps figured it out".

Push your green phone button once
Then push the blackberry key next to it once
Scroll down and choose Options
Then choose General Options
Scroll down to Default Call Volume
If set to "Previous" reset to 50%.
Then save.
This will help with most echo issues until Sprint updates us. Some people that call you may have an echo yet but most won't. It worked for me and a few coworkers.

If you people would read the original statement COMPLETLY, you would see that "The root cause of the voice echo issue has been identified and is being addressed in a software release MR2 that should be available in March." I just downloaded the newest patch and it fixed my txt msg problem. Mine works great now.

I just want to say that Sprint is the worst, most thoroughly incompetent, most aggravating, most arrogant, least helpful service provider I have ever, in my life, dealt with.

I spent more than 18 hours of a 44 hour period (all while I was trying to close escrow on the sale of my house) trying to help them reinstate my phone service after a rep I was on the phone with accidentally cut it off. I must have gone through the convoluted phone reinitialization process more than a dozen times before I finally told them that was the last try. (I actually gave them one last chance when one of the least helpful or pleasant people I'd dealt with in a long line of overconfident, supposedly overeducated [many of them claimed to have MS degrees in IT] all but pleaded with me -- still without being friendly or pleasant. I gave them that last chance, went through the ten plus minutes of song and dance and then, they dropped yet another service call in the middle -- that had happened a number of times -- and I got in my car and drove down to Circuit City and bought a T-Mobile phone and never, ever looked back.)

In my experience, Sprint are incompetent, insufferably arrogant, and one thoroughly unpleasant company to deal with.