HELP! Call failed/SOS/insufficient coverage???
 

I got a Blackberry Bold 9780 this summer however I've begun to have problems with it. Almost everytime I try to make a phone call, it says "Call Failed" or go into SOS mode even when I should be in full coverage areas. If I try to go on the internet, it says "insufficient coverage. Please contact your service provider" and my bbms take a while to send. If I am in a wifi zone such as my house or school, the data works perfectly once connected - calls still have the same problem. I've tried rebooting the battery, wiping the phone completely, updating it on Device hardware, and got a new sim card. Nothing seems to work! I have blackberry insurance but they will just replace the phone for $150 and I'd rather not spend more money than I did on the phone originally.

Thanks so much!!!
Posted via BlackBerryForums.com Mobile

Re: HELP! Call failed/SOS/insufficient coverage???
 

Does this happen at one particular location or in nearby locations?

Did you drop it or get it wet?

I see that you have done a battery pull. Have you re-registered via the host routing table?

Resent service books?

Called the carrier?

Re: HELP! Call failed/SOS/insufficient coverage???
 

It happens almost everywhere. The bbms eventually send (maybe 10 min later) but phone calls still fail 75% of the time. People who try to call me get a busy tone or if I'm able to pick up I hear static buzzing and it disconnects.
I registered wifi and the gprs ca 302 ..... Under host routing tables. And I'm not sure how to reservice the books.
I haven't gotten it wet, and I'm really careful with it (it hasn't really fallen from anywhere significantly high)
Posted via BlackBerryForums.com Mobile

Re: HELP! Call failed/SOS/insufficient coverage???
 

gprs ca 302?

See the FAQ on resending service books.

Did you call your carrier?

Re: HELP! Call failed/SOS/insufficient coverage???
 

Hi nmorets,

I am having the exact same issue with Bell as well. I have two separate 9780's with Bell, one personal, one corporate on BES, and same issue occurs with both frequently.

Have you found a solution to this at all??