“ Originally Posted by pdenbigh 
”
I much prefer to post solutions rather than questions but I'm afraid I have to ask for some help.
I have a Verizon XV6800, purchased yesterday. I am competent with computers, have hacked my old Razr quite a bit.
Also, I searched for this on the forum b/c I hate redundant questions. I searched the following queries:
- verizon unauthorized, -verizon unable authenticate, -#8899, and a few others, but unfortunately turned up nothing despite reading all 16 pages of a few threads :-).
...SO, here's the problem. I started by flashing just as the instructions suggest, w/o unlocking the phone. When I did this, the program said "Unable to verify phone" or something similar. So, I unlocked the phone and the rom installed flawlessly. I reset the phone before it "applied customizations."
It boots great and looks like all is well. However, when I Try to make a call, it goes to verizon with a message stating they are unable to authenticate my phone.
I did a *228 and did both options, 1 to program phone, 2 to update PLR (just in case!), and no luck.
I have a feeling it has to do with a few abbreviations I've seen around here, something like MMS, SMM, etc.
To correct this, should I just call verizon and activate the phone? Is there a code generator/etc/tutorial on doing this w/o calling?
Thanks in advance and sorry if this has been addressed.
Peter
--------- New Post Merged on 7/10/2008 at 02:25:34 --------
P.S. I can get on the internet fine... just can't make (or receive) calls.
--------- New Post Merged on 7/10/2008 at 02:35:14 --------
PS 2 - the phone shows my proper phone # under "My phone number"
--------- New Post Merged on 7/10/2008 at 03:08:45 --------
***SOLVED!!***
A little more google action revieled other's with this problem, and their solution was to call Verizon. I did, told them I did a "windows update" (literllay!) and started having problems.
They did the *228 thing, I told them I'd tried but that I would happily try again, but of course no luck.
I told her I'd done a bit of searching and found that similar problems were resolved with an new A-record. She transferred me to tech support who immeidately gave me a new A-record, entered it, rebooted, and all is well now!
Now, on to playing with the GPS :-).
Thanks for this awesome resource guys and gals!
glad you got it but that has been discussed and solved many times............ after every hard reset you will have to do that :<