Instinct problems

£

£å§hïöñ GåwÐ

New member
I'm flashing a friend's Intinct to cricket and everything's working fine except I can't send texts. I can receive them fine but not send. The phone can make and receive calls, he doesn't have web with cricket so I'm not doing that part. If I send him a text from my phone he gets it fine, but when I send one back from his phone it says "Network not responding. Saved in outbox." Am I missing a step? I can't find any tuts on this problem. Thanks
 
Its been mentioned numerous times, I feel like my market was the first victim, but it's a NETWORK GLITCH if you're outgoing text fail, call cricket request an ACCOUNT REFRESH, should fix problem after they refresh it, may take up to 30minutes
 
Wirelessly posted (XV6700: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; PPC; 240x320) Opera 8.65 [en])



oh i see. would it matter that he activated his line just today? so the flash was succesful then? ill tell him to ask for the account refresh. thanks
 
it didnt work, he got it refreshed and I even updated the prl again just in case. still nothing. are there any other things you can think of as to why it wouldn't work? oh, he ported his nuraber also from Sprint to Cricket. I remeraber when I ported my nuraber from Virgin to Cricket, I couldn't get texts from people on Tmobile and Cingular (back then), which was an ODD thing to happen but cricket eventually figured it out.
 
Sometimes when you call customer service you may get a rep that either doesn't know how to refresh the account or simply doesn't want to. The best solution is to take it to a Cricket store and have them do it for you. I get a few of them every now and then and the cricket store fixes it everytime.
 
If he ported his nuraber, it may take up to a week for SMS, seen it happen. Either way, it may take several "refreshes" You just have to get the right rep to correct the account, most of the time SMS is not added with CID and foreign phones.

The only way it could be a phone issue is the following:

- MO_SMS nv items have been changed to something incompatible
- The customer has a custom signature that has characters not supported by Cricket
e.g. Had a customer that had a signature like this: $a1*!~`
- Last one I've seen is corrupt message in messaging, empty out the message center
 
Back
Top