Hard rest of VX-6800

[old_school_dave]

Last Saturday I upgraded my VX-6600 to the VX6800, and everything is going OK, except one problem I'm hoping someone has seen before (and might know a workaround).

So I was playing with trials of different software, and did a hard reset via Settings > System > Clear Memory. Once the PPC came back, I would get an authorization error when trying to use the phone.

Today I went into the Verizon store to see why the phone stopped working. The tech there couldn't get it working, so he unboxed another 6800 for me. That one worked fine. Just for kicks, I had him do a hard reset (he did the stylus plus two soft buttons). After the reset (and *228 for programming), the second phone couldn't dial out.

It looks like to me that the hard reset is removing some VZW-specific information from the phone. The tech at VZW had someone on the phone who generated a new "A-key" (at least that's what I overheard).

So my phone is working again, but I'm pretty sure the next time I go to hard reset, the phone function will be toast again. Has anyone run into this issue? Having to call VZW after every hard reset just doesn't seem right to me.

Also, is there a different between the "software" hard reset I did, and using the soft reset plus holding down the two soft buttons?

Thanks! Dave

[g60corrado]

yeah, its a known software issue that htc and windows are working on, i dont know when they will come out with the fix, but from what i understand anytime we xv6800 and smt5800 users do a hard reset are phones can no longer authenticate on the vzw network. fixing is pretty straight forward, but you will need someone to gen. an a-key for you. soft resets are ok. . .lol.

[old_school_dave]

At least it's not just me...

So after a hard reset, is it known that someone has to generate a new a-key, or if I have my existing one, can I use that one? Just trying to stay away from VZW tech phone support if at all possible, but it's probably just wishful thinking.

[rmancl]

from what i've read you can reuse the a key every time you do a hard reset

[g60corrado]

no you cant reuse an akey. its a randomly generated 26 digit number that always changes, but all you would have to do is call WDTS or dial #whatever that the poerator says if you try making an outgoing call after doing a hard reset. it connects you to the fraud department(dont worry, your not getting in trouble, lol). so no, you dont ahve to go into a store, as most techs will not know what to do

[drakx188]

i just did a hard reset and my phone doesnt work now....

what number do you call and how do you get an a key

[SecretAgentMan]

Originally Posted by drakx188

i just did a hard reset and my phone doesnt work now....

what number do you call and how do you get an a key

I have read, but never personally tried, that you can get a new akey by going online and switching your esn to an older phone (if you have one). During the process, if your phone doesn't support data, you'll be prompted to remove the data plan (remove it . .you'll get it back when you put your phone back). You can then switch back to your phone, put the data plan back on it, and re-program your phone (*22. A new akey will be generated.

[jason25]

Originally Posted by drakx188

i just did a hard reset and my phone doesnt work now....

what number do you call and how do you get an a key

Originally Posted by g60corrado

...all you would have to do is call WDTS or dial #whatever that the operator says if you try making an outgoing call after doing a hard reset.

did you try this?

[weedahoe]

I had to use a different phone to call into VZW to get thier CSRs to get me an A-key last time because the message my phone was giving me would only let me dial a collect numbers or use a calling card. It didnt give another number to use and route me to anyone live. So call your carrier or go visit them.

[jmorton10]

I have hard reset my Verizon XV6800 probably 10 times & only once did it need a new A-key. All the other times all I did was a *228 option 1 then 2 or nothing at all (sometimes the phone worked fine right after the hard reset)

~John