[rmartin]

Just started getting this error while trying to send a text. I've tried pulling battery/restarting, doesn't help. I recetly installed appbrain app and it did some updates to 'talkback', 'google streetview', and amazon mp3. I uninstalled these updates and still get this error. I can receive texts fine. Has anyone seen this, do I need to call Sprint?

[njbianco#AC]

You need to call sprint.

[zeropcs]

I have seen an error close to this before, did your city recently start requiring you dial all 10 digits to place a call instead of 7?

[rmartin]

No, I don't think so, my wife also has an Epic on the same plan and she can send texts fine. I ended up doing a hard reset and its working now. Not sure what would have caused this.

[Tecchief]

Got similar message a few days ago, started when I tried to send an invite via text for TiKL, I took it in for service, guy at the store/my best friend, tried everything, ultimately had to reset the phone.

I just tried today to send that invite again via text, error message comes back. Just updated the PRL and rebooted the phone looks like its gone again. I think it might be related to the app but I can't be sure yet.

[eriksseven]

I've also had this happen several times a few days ago. What I did was deleted the "text message thread" -- or the back and forth conversation I'd been having with the person. Then I went back to my contacts list and started a NEW text message for them (starting over essentially).

For whatever reason this seemed to create a "good" phone number...

*FYI* I also didn't think about this as being a LARGER issue--I thought it was probably due to the CRAPPY service I have at my house. This is what led me to try several things, including what I just mentioned.

[aceboogie]

Had this problem and just set up contacts as mobile and it works for me

[tp72]

I've had this same problem with the same person. I always have to restart my phone.

[egeorge1]

My wife has been having this trouble. She found when she changed her contact number to include the area code it worked fine. I haven't had this issue because I always save contacts with the area code included.

[Rderosier86]

im getting the same issue and just install tikl

[rmartin]

I got this problem right after I installed tikl also. Uninstalling didn't help, I ended up doing a hard reset to fix the problem.

[estebancam]

Everyone here needs to go to

about phone>system updates> update profile

All the PRL does is update your Preferred Roaming List, in other words, it finds towers that the phone might not have known were there, and it selects the towers to connect to next time you are in that area, as it puts them in a preferred list.

Updating your profile is what really changes things. It basically re-activates your device on the network. I'm not 100% sure if updating your profile will work, but give it a try. It usually solves every network issue I ever have.

[pablomentabo]

im getting the same issue and just install tikl

I just had the same issue after installing TiKL too. The way I fixed it was by going to the contact that I tried to contact in TiKL and deleted all the text messages I had in the built in texting app's history (the whole thread of txts at once). I did this after TiKL was uninstalled but IDK if that really matters. I know one thing, if this is how TiKL will affect my phone then I am not going to try this app out again, I'll stick to txt or sending recorded voice over MMS instead

[tlab]

I had the Code 0: Bad phone number when using google voice search when I would send text to ... I would try and text my wife with voice commands and I would get this error, but I could send a text manually with no problem. I had the word "[wife]" in her contact in case of an emergency someone could call my wife. I took out the [wife] part and it stopped giving me the bad phone number error.