Quote:
Originally Posted by Whosdaman
turn off roam then
|
I had the same problem with both my phone and my wife's after the leaked ROM upgrade. Sometimes I would get a message saying Welcome to America's Roaming Network and sometimes Verizon would tell me my phone was not able to be authenticated. I called Sprint's Advanced Tech Support (ask for 'Aircard' when dialing the CS number) and he had to make changes on the network side to allow me to roam, but we had to switch the phone into Roam Only for him to see which towers were not allowing it (or so he said). It had to be exhibiting the problem at the time (which means you have to call them from a land-line). Whatever he did, it worked and we verified by switching to Sprint Only, Roam Only and Automatic where I could catch both Sprint and Verizon's signals. Both phones have been fine ever since, even after the newest radio upgrade. He warned me that the problem could come back if I traveled to a different area.
On another forum, I have read that you need to have them reset the HLR and reprogram the phone. He didn't reprogram my phone at all and he said that the Home Location Register wouldn't solve this. The problem is actually on Verizon's end (or so he claimed). I've seen that lots of Verizon customers are having to call CS and have their phone re-authenticated after a hard-reset, so perhaps he was telling the truth. (I think I found a post about that on XDA).
PS...he actually referred me to PPCGeeks for helpful hints on common problems! Little did he know that I've been a kitchen user since the early days of the Apache!
PPS...He also claimed that a new upgrade was coming in a few days that would fix the standby missing calls bug, so hopefuly the new official ROM will finally fix it. I have been using S2U2 and setting it to 'blank screen only' as a work around...not as battery friendly, but at least I get my calls!
Anyway, call CS and make sure you get to Advanced Tech Support. The regular folks don't have a clue when it comes to the WM phones.