My phone would not authenticate after flashing to the new radio and DCD's 2.0 rom. So I called Verizon and they gave me my A-KEY, I wrote it down in case I would need it again. After four days on DCD's 2.0 I decided to give The "FallingAngel12 rom" a go I flashed the r3 version and my phone can no longer authenticate. So I grabbed the A-KEY that I wrote down (this was triple checked with the VZW rep) I put in my A-KEY and saved the changes, it reset the device, then I did a *228 option 1. Still no good on the authentication, so it looks like I will need to call VZW again, which I don't mind doing, but eventually if I keep flashing my phone on a weekly basis to try out the new roms that will surely be popping up, Verizon is going to probably get wise to the fact that I am calling to fix authentication every few days.
I have read posts of Verizon users that have not had any problems with the authentication after flashing, so has anyone figured out a way to not lose authentication?
PRSPower said:
My phone would not authenticate after flashing to the new radio and DCD's 2.0 rom. So I called Verizon and they gave me my A-KEY, I wrote it down in case I would need it again. After four days on DCD's 2.0 I decided to give The "FallingAngel12 rom" a go I flashed the r3 version and my phone can no longer authenticate. So I grabbed the A-KEY that I wrote down (this was triple checked with the VZW rep) I put in my A-KEY and saved the changes, it reset the device, then I did a *228 option 1. Still no good on the authentication, so it looks like I will need to call VZW again, which I don't mind doing, but eventually if I keep flashing my phone on a weekly basis to try out the new roms that will surely be popping up, Verizon is going to probably get wise to the fact that I am calling to fix authentication every few days.
I have read posts of Verizon users that have not had any problems with the authentication after flashing, so has anyone figured out a way to not lose authentication?
Click to expand...
Click to collapse
What do they have to "Get wise" to? I'm not intimately familiar with Verizon's policies, but how can they tell you not to hard-reset your device? That's just silly.
As far as I know a hard reset will not make you loose the authentication info, only a rom/radio flash. And since they have not release any kind of rom upgrade for the Titan it would not be hard for them to figure out what I have really been up to. I just don't want them to invalidate the warranty on my phone.
PRSPower said:
As far as I know a hard reset will not make you loose the authentication info, only a rom/radio flash. And since they have not release any kind of rom upgrade for the Titan it would not be hard for them to figure out what I have really been up to. I just don't want them to invalidate the warranty on my phone.
Click to expand...
Click to collapse
Understandable... but unlikely. How do they know that you aren't reflashing with the original ROM over and over? It'd be pretty tough for them to prove you were reflashing with some hacked ROM. I doubt they'll invalidate your warranty, but does anyone else want to check in on this?
very strange, after flashing, my mogul can't roam on vzw at home w/ authentication error using prl 60610/60611. while it is still able to do so at my office. :-(
don't know which one i should call, vzw or sprint?
So I called Verizon for my second time to get my A-KEY, this time it was a completely different A-KEY than the last time. Instead of calling the 800 number and getting the PDA group first to be transfered over to the "Authentication and Activation group" I just called #8899 from my phone like the could not authenticate message directs, and it got me directly to an authentication specialist with no waiting, which was nice.
She commented that this was my second time calling for authentication problems, and I gave her the "I am a developer and frequently hard reset my phone" line. She called me back on a land line and then walked me through the #778 method to input my A-KEY. So I am back in action.
She did happen to make a noteworthy comment. I mentioned that this never used to happen on my 6700 and I hard reset that all the time, to which she said. We have noticed that losing the authentication information is a problem when hard reseting these 6800's and we have been in contact with the manufacturer so that they can provide an update to fix the problem.
Take that comment for what it is worth.
PRSPower said:
So I called Verizon for my second time to get my A-KEY, this time it was a completely different A-KEY than the last time. Instead of calling the 800 number and getting the PDA group first to be transfered over to the "Authentication and Activation group" I just called #8899 from my phone like the could not authenticate message directs, and it got me directly to an authentication specialist with no waiting, which was nice.
She commented that this was my second time calling for authentication problems, and I gave her the "I am a developer and frequently hard reset my phone" line. She called me back on a land line and then walked me through the #778 method to input my A-KEY. So I am back in action.
She did happen to make a noteworthy comment. I mentioned that this never used to happen on my 6700 and I hard reset that all the time, to which she said. We have noticed that losing the authentication information is a problem when hard reseting these 6800's and we have been in contact with the manufacturer so that they can provide an update to fix the problem.
Take that comment for what it is worth.
Click to expand...
Click to collapse
One wonders if that problem has suddenly come to light in the last few days due to customers calling with authentication problems.
PRSPower said:
As far as I know a hard reset will not make you loose the authentication info, only a rom/radio flash. And since they have not release any kind of rom upgrade for the Titan it would not be hard for them to figure out what I have really been up to. I just don't want them to invalidate the warranty on my phone.
Click to expand...
Click to collapse
Not true. I recently had to return my phone for an exchange and did a hard reset to clear all of my info. To continue using it prior to the exchange I needed a new a-key. At that point I had never updated the rom on my phone. It doesn't need it every time you hard reset because I have done it at least 5 times that it didn't need anything but there are times that a hard reset does require authentication.
PRSPower said:
As far as I know a hard reset will not make you loose the authentication info, only a rom/radio flash. And since they have not release any kind of rom upgrade for the Titan it would not be hard for them to figure out what I have really been up to. I just don't want them to invalidate the warranty on my phone.
Click to expand...
Click to collapse
not necessarily true. When I first got my phone and I was messing around installing all kinds of new apps (no ROM's, just apps), I hard reset my phone 4 or 5 times in less than 12 hours. I had to call to get a new A-key.
brouski said:
One wonders if that problem has suddenly come to light in the last few days due to customers calling with authentication problems.
Click to expand...
Click to collapse
VZW told me the same thing in the middle of December when I got the XV6800. I had to hard reset it and then call for the A-Key. She said, "This is a known issue and we are waiting on the manufacturer to provide a fix. But call as many times as you need to, to retrieve your A-Key. We understand these phones are new (to us) and are not perfect."
I quess I have been lucky. I have flashed my phone a dozen times at least and never had a problem with this. Of course, now that I've said this I probably will.
According to the verizon rep I spoke with, the A-key is generated anew each time, so saving the old key won't work.
I don't think anyone has anything to worry about. If you need a line, tell them you're a WM developer who's testing on his device, and need to hard reset it fairly frequently to test your application install.
xzxzzx said:
According to the verizon rep I spoke with, the A-key is generated anew each time, so saving the old key won't work.
I don't think anyone has anything to worry about. If you need a line, tell them you're a WM developer who's testing on his device, and need to hard reset it fairly frequently to test your application install.
Click to expand...
Click to collapse
yeah they gave me a new A-Key and it didn't even work.... they had to re-authenticate me remotely
Flashed this time and did not loose authentiction.
So flashing from DCD's 1.6.10 to DCD's 2.0.0 BETA I lost my authentication.
Flashing from 2.0.0 to angel12's rom I lost authentication.
Flashing from angel12's rom to DCD's 2.1.0 rom I DID NOT loose my authentication.
There really seems to be no rhyme or reason as to why or when the authentication gets jacked.
With so much action going on in ROM development for the Titan, I have a feeling I will be flashing a new rom at least twice a week. But the amazing advancements made possible by the cooks and hackers here at xda make every call to Verizon worth it.
Simple A-KEY Fix
Login to your VZW account online, change your ESN (you need another VZW ESN ... an old phone's ESN will do), change your ESN back to the phone you flashed, dial *228. VZW will not update your A-Key in the phone unless your ESN was just changed!
PS: Junior Member my ___!!!
can you expand on this
Can I get a little bit more info on the ESN change thing. How will this affect Verizon and their A-KEY crap?
dj13241 said:
Login to your VZW account online, change your ESN (you need another VZW ESN ... an old phone's ESN will do), change your ESN back to the phone you flashed, dial *228. VZW will not update your A-Key in the phone unless your ESN was just changed!
PS: Junior Member my ___!!!
Click to expand...
Click to collapse
I pulled an all-nighter trying to fix this and that method actually worked perfect. I can't believe it was that easy. Quetion of the day, how do you find your A-Key? Before I flashed my ROM, I went into the ##778 to write down my A-Key and the field was blank. Im just wondering what I could have done to prevent this from happening.
Thanks!
I pulled an all-nighter trying to fix this and that method actually worked perfect. I can't believe it was that easy. Quetion of the day, how do you find your A-Key? Before I flashed my ROM, I went into the ##778 to write down my A-Key and the field was blank. Im just wondering what I could have done to prevent this from happening.
Thanks!
Click to expand...
Click to collapse
The A-Key is never shown in EPST. It is always blank. It's not used by your phone to connect to the network like your MDN or MSID, instead it is used once to authenticate your ESN, then discarded. This is why the A-Key is different each time you need to re-authenticate and why it is not stored. The VZW tech support rep generates an A-Key and then tries to authenticate you via OTA *228. If this fails, this is why you have the A-Key field in EPST. You can manually enter it, authenticate with the A-Key the rep generated for you, then it is discarded.
MstaCDLite said:
I pulled an all-nighter trying to fix this and that method actually worked perfect. I can't believe it was that easy. Quetion of the day, how do you find your A-Key? Before I flashed my ROM, I went into the ##778 to write down my A-Key and the field was blank. Im just wondering what I could have done to prevent this from happening.
Thanks!
Click to expand...
Click to collapse
It's completely normal to see no A-Key with a XV6800. The verizon A-Key is only good for one use. Next time you reboot your phone it will be gone. You should see a blank space in the A-Key field in ##778
If you need to authenticate again due to a radio flash, then a new A-Key is required.
Note this advice is specific to verizon XV6800 titans. They lose their authentication when changing from a non-gps radio to a gps radio. Or when hard reseting the stock rom.
Verizon will not question you for requesting A-Keys again and again. Just say you did a hard reset and that you cannot make calls now. Hard resets of the STOCK rom cause you to lose authentication, but not hard resets of custom roms. But as long as VZW think you hard reset a stock rom then they wont worry about issuing A-Keys.
Painless
The first, and only, time I flashed my radio it would not authenticate. I also dialed #8899, got straight to the right person and he updated my phone remotely. I simply said my phone "gave me this message and directed me here". He fixed it no questions asked.
Was painless and very fast. Good to know that I'm a developer and frequently hard reset my phone, should they ask in the future.
Given that this is very easy, very fast, can be done directly from the cell phone and requires no further input on my part, it seems the way to go.
Related
It left all kinds of Sprint stuff in the EPST, not sure how to clean that up, or if I'm screwed.
Anyone know of a way to get it all restored back to Verizon acceptable?
I have the 2.4 SPD, Radio 3.27, and DCD 2.2.6 and expect for no phone service, love it.
I've called Verizon, they have not been helpful, I did check my a-key both before and after and it was blank both times.
Help?
Fred Rat said:
It left all kinds of Sprint stuff in the EPST, not sure how to clean that up, or if I'm screwed.
Anyone know of a way to get it all restored back to Verizon acceptable?
I have the 2.4 SPD, Radio 3.27, and DCD 2.2.6 and expect for no phone service, love it.
I've called Verizon, they have not been helpful, I did check my a-key both before and after and it was blank both times.
Help?
Click to expand...
Click to collapse
I don't know if it will work, but try going into the phone app and dialing ##786 Talk
This is supposed to completely reset the device, including the EPST settings, to factory clean. You will need to restore the MSID and MDN, so make sure you know what they are. I do not know if you will need to obtain an a-key from VZW. After that you will probably need to do the *228 setup.
If that does not work, maybe reflashing the radio and Verizon ROM will help.
I've got it fixed
Thanks for the tip; while I was waiting for that I tried a number of things, one of which worked.
What I did was to reflash the stock verizon rom from
http://forum.xda-developers.com/showthread.php?t=359659&page=2
Using the complete version.
This put back the original radio and rom.
When I rebooted after that, it ran some cabs on first boot. One of them was called something like ResetRadio. Anyway after that I was able to call *228 and could do both options 1 and 2. Which I could not do successfully before.
I was still getting unauthenticated messages when I tried to call anyone, and could not take incoming calls.
I then called VZW and got a new A-Key, that fixed the phone so I could call in/out, but internet access was still broken.
They had me take my battery out, while they did something on their end; after that we redid the *228 and internet access is now working. We did a test text message and that worked as well.
I think the key in all of this, is to NOT flash the Sprint ROM into a Verizon phone, but if you do, you can reflash the Verizon version to put things back in order from the link I mentioned above.
I am using a DCD rom 2.2.6, and while I am a noob on some of this, I seem to recall him mentioning that he no longer includes the extended ROM; if that includes the part that resets the radio on a hard reset, I think it's actually required for people to keep their sanity.
Hope this helps, and for those that are worried that they will screw up their phones and have no way back from the far side of disaster, I can say that I've been there and made my way back.
Best of luck to you all.
DCD 2.2.6, GPS, and yes I can even make phone calls!
Ok, I jumped into upgrading the ROM on the xv6800 I picked up from Verizon earlier today. After lots of looking around, I determined that I needed and located the SPL / bootloader (Olipro 2.40), a custom ROM cooked up courtesy of DCD, and the 3.27 Radio ROM.
Got the bootloader going, upgraded the ROM and got the dreaded locked Verizon screen. Didn't take long to figure out I needed to load the Radio ROM so I then got that loaded.
Immediately I started getting the message that my phone needed to be programmed, so I started to dial *228 but my phone just said "Call Lost" or something along those lines. Then I noticed it was just searching for signal continuously.
Weird thing is, after a LONG while (as I searched this forum for a couple of hours and tried and re-tried flashing the ROMS) I had signal, I did the OTA programming and upon reboot lost signal again.
I have now used the relock tool to return to the official Verizon ROM and I now have signal again. However, I have to call in for the AKEY.
Anybody else experience complete loss of signal? (not the data drop issue)
Edit: Just a side note, I called VZW tech support and basically admitted to flashing the ROM and flashing back. He wanted to know how I knew about the AKEY...told him I had been in wireless for years (true, but years ago as well) and was very knowledgeable. He shrugged it off and was happy to give me the key. I'm back up and running, but a bit gun shy to go flash the ROM again tonight. What time does VZW tech support shut down??? LOL
Im on sprint but changing my Mobile IP Settings helped me fixed this same problem.
limezednem said:
Im on sprint but changing my Mobile IP Settings helped me fixed this same problem.
Click to expand...
Click to collapse
Did you copy these from the EPST before you flashed the ROM?
Oh yeah, forgot to mention that I re-entered the MSID and the MDN.
Still can't connect to data....probably have to call tech support again soon. blah...
try using the msid and reset your ip to Mobi'e Prefoired
sandiegodude said:
try using the msid and reset your ip to Mobi'e Prefoired
Click to expand...
Click to collapse
Can you explain a bit further? Are you talking about MIP_MODE? That is set to "Mobile IP Preferred"
Ok, so I tried again and it happened again. I'm sitting here looking at a phone that is constantly searching.
This time the MSID and MDN are intact.
Any suggestions?? Which IP settings would I be checking and what should I be setting them to?
And as before, I now have signal about 20 minutes later (faster this time than last night.)
I need to do an OTA programming, I'm sure it will die again after the reboot.
Programming now.....rebooting.....and it's dead again. Any thoughts?????
Edit: Almost 20 minutes later again and I have signal, but not authorized again...guess I'm calling support for the A Key once more. Soft reset takes signal offline again.
I'm running a NexVision ROM based on DCD's 2.2.4, Sprint network. This issue happened to me three times, but not until after I loaded PRL 60711 (with Sprint). Was probably just a coincidence, though. Since then, it's been fine for a week.
Well, it came back up again. So it looks like I've narrowed it down to just a long delay in acquiring signal.
I'm on the phone w/ VZW now getting my A Key once again.
I dont know much about verizon but isnt the Akey always the same? Also, try toggling the MIP back and forth a few times. That has worked for some of us.
The A Key changes each time on VZW from what I understand. That comes from sources on here as well as VZW techs. I didn't write it down today and the one I did write down last night is @ the office so I have no way to compare for a definitive answer.
What would I toggle the key back and forth from/to? Can you explain that in a bit more detail? THX
Edit: Is this what you were suggesting? Under M.IP Settings
Changed MIP_MODE to Mobile IP Only then reset
Changed to Simple IP Only then reset
Changed to and back to Mobile IP Preferred
Tried and no go.
Sorry to hear it didn't work. It seemed to have helped a couple of us in this thread. Maybe it might take a couple more tries. But we all seem to be having the same problem.
Just found this post:
http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1
Tried again...no good. Maybe I'll try a few more times just for posterity.
Geckotek said:
Just found this post:
http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1
Tried again...no good. Maybe I'll try a few more times just for posterity.
Click to expand...
Click to collapse
Well, good luck! Haha
limezednem said:
I dont know much about verizon but isnt the Akey always the same? Also, try toggling the MIP back and forth a few times. That has worked for some of us.
Click to expand...
Click to collapse
Verizon isn't using the a-key (at least not in all locations) to validate the phone. They have some other authentication in house that gets reset by them. My a-key is blank, but after the update, I had to authenticate my phone to be able to make calls.
It appears they use both because they have given it to me twice now.
But back to the task @ hand...does anybody have a guess at why it would take 15+ minutes to acquire signal?
I did find one temp solution on my VZW phone:
after a reset, while the phone is searching for a signal, I went to the phone func and entered *22803. It then finds a roaming signal and starts "programming". At that point I hit call end and it picks up the signal and goes to EV, full bars. The phone says programming unsuccessful, but if I close the phone and re-open it, everything is fine.
pkp190 said:
I was also having this problem, what I did that fixed the problem was i reentered the MSID and MDN in the ##MSL# screen. Then allowed the phone to reset. from that point forward I get signal as soon as it powers on from reset. Hope this helps.
Click to expand...
Click to collapse
Thanks pkp190!!!!
Edit: Spoke too soon. After another *228 the problem has returned and trying it again didn't fix it this time.
radio
It seems to my feeble mind that the problem your are experiencing is caused by the flaky 3.27 radio rom. Its the very reason I have, unfortunately, given up on the gps roms. Some people report no problems at all, and others report serious issues. For me it was a problem so I gave up and went back to dcd1.7.0 which I find to be the best rom yet.
Some people have reported that toggling MIP settings (see http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1) helps but for me it didn't work. You could try that and see if it helps your case.
Others have reported that recooking a new rom with fewer OEMs might solve the problem. Once again, for me, it didn't work.
Otherwise, you might have to just wait for a new radio to be "officially" released before gps is a reality for you.
Geckotek said:
The A Key changes each time on VZW from what I understand. That comes from sources on here as well as VZW techs. I didn't write it down today and the one I did write down last night is @ the office so I have no way to compare for a definitive answer.
What would I toggle the key back and forth from/to? Can you explain that in a bit more detail? THX
Edit: Is this what you were suggesting? Under M.IP Settings
Changed MIP_MODE to Mobile IP Only then reset
Changed to Simple IP Only then reset
Changed to and back to Mobile IP Preferred
Tried and no go.
Click to expand...
Click to collapse
I think that in areas where the A-key is still used you can consider the a-key like a serial number for a piece of software (in this case ur authenticating into the verizon network).. there is an algorithm based on your ESN and any random number of keys can be generated to fit the algorithm and be accepted.
In other words although they may give you different A-keys every time that you call all of them are equally valid and can be entered to authenticate into the network.
Its like a keygen for pirated software when u can keep hitting that generate button to make random keys but all of them work in theory(not that I have ever contemplated using or used pirated goods)
I am helping my mom with her VX6800 for verizon. I first flashed the RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4 350H_SPCS_AM_Ship ROM, just to get the radio from it (If anyone knows where to get the entire Ship ROM with 3.42.30 please tell me, can't find it). I then flashed DCD 3.2.2 and then installed the Verizon carrier cab.
The phone was working right away to make calls, although it still showed Sprint on it, as opposed to Verizon. When i try to access the internet it gives me an error saying "Dialed #777, Cannot connect for unknown reason." I had flashed a verizon phone for a friend before and had to call verizon to get a new code, doesn't seem like the issue here but not sure why i'm not getting internet service and if it has anything to do with the sprint logo showing on the screen..
TIA!!
Sounds like maybe you let the sprint ROM reboot (reset) after you flashed it to get the radio? Check the Titan WIKI on XDA and it'll tell you everything you need to know to fix it.
worthingtonmedic38 said:
Sounds like maybe you let the sprint ROM reboot (reset) after you flashed it to get the radio? Check the Titan WIKI on XDA and it'll tell you everything you need to know to fix it.
Click to expand...
Click to collapse
I have read through the Wiki a few times and it doesn't say anything in there about the ROM rebooting or resetting
"To flash, enter bootloader mode by pressing the power, camera button and then the reset button. The screen should be at a three colored (red, Blue and Green) screen, check to make sure you have the appropriate bootloader. Then plug the device and computer into the USB cable. Start the RUU.exe upgrade program on the PC that usually is provided with the ROM."
I did all this, except not sure if i am using a RUU utility, i just double click on the ROM icon,which i think has the RUU built in. It then flashes the SPrint ROM. if i am supposed to do something after it has finished flashing to prevent it from rebooting or resetting i couldn't find it in the wiki, so if u can just tell me that would help me out a lot...thanks heaps
you let the customizations run... end of discussion...
i think at this point, it'd be easiest for you to flash back to Verizon STOCK and then follow my guide to upgrade it (see signature)..
To flash back to stock, see the info from: http://forum.xda-developers.com/showthread.php?t=376873
You need to reset before the carrier customizations kick in. If you didn't then that is why you have the Sprint info on your phone.
There are a bunch of threads here about this problem. Let me see if I can find a link to one.
Here is some more info from the wiki:
do NOT boot into the OS after flashing to any of these ROMs.. After screen calibration the carrier customisations will run and alter your EPST settings to that operator's settings.
OOPS! You just let the customisations run but are with a different carrier than the ROM you just flashed to!
Choose A or B
A.follow above EPST instructions in step I to edit back to the settings that you recorded
B.Goto to the Titan Stock Page to restore your device back your carrier's default settings, boot into the OS and permit the cusomisations to run, and then return back here to start over again.
Click to expand...
Click to collapse
you dont need to reset at all. ugh. follow these steps:
1) flash sprint rom
2) at 'tap screen to set up device' flash your rom of choice
3) install carrier cab
4) soft reset
literally, its that simple. if you need a step by step, i guess here you go:
1) flash sprint rom
no need to enter bootloader unless your installing from SD​2) after rom installs, it will automatically reset
3) at 'tap screen to set up device', unplug and plug your phone back in
4)run (assuming you are using DCD) the kitchen or the RUU.
phone will reset after done installing​5) calibrate the screen and let customizations run
6) install carrier cab
7) soft reset
done
Dillsnik said:
I am helping my mom with her VX6800 for verizon. I first flashed the RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4 350H_SPCS_AM_Ship ROM, just to get the radio from it (If anyone knows where to get the entire Ship ROM with 3.42.30 please tell me, can't find it). I then flashed DCD 3.2.2 and then installed the Verizon carrier cab.
The phone was working right away to make calls, although it still showed Sprint on it, as opposed to Verizon. When i try to access the internet it gives me an error saying "Dialed #777, Cannot connect for unknown reason." I had flashed a verizon phone for a friend before and had to call verizon to get a new code, doesn't seem like the issue here but not sure why i'm not getting internet service and if it has anything to do with the sprint logo showing on the screen..
TIA!!
Click to expand...
Click to collapse
Hi there,
The 3.42.30 Radio was pulled from a Vogue and was modified to work with there Titan, therefore there is no ship ROM for it. Your best bet is to format an SD card with the FAT32 filesystem and copy the TITAIMG.NBH onto it and load up in bootloader mode. There are thorough instructions in the Titan wiki. Best of luck!
Hate to break it to you all, but if he let customizations run...then he's screwed unless he can get Verizon to issue him a DMU reset. If not, the phone needs to be replaced. End of story.
damn....I had to get a new phone after my first time flashing too...
gc14 said:
Hate to break it to you all, but if he let customizations run...then he's screwed unless he can get Verizon to issue him a DMU reset. If not, the phone needs to be replaced. End of story.
Click to expand...
Click to collapse
Are you serious?? oh no
How would you go about asking vzw for a DMU reset? i'm not sure what that is....and would vzw do a phone replacement??? they won't say it was voided?
Thanks all for all your help...i haven't had a chance to reflash anything yet, but gonna give it a go later today and pray it works!
Dillsnik said:
Are you serious?? oh no
How would you go about asking vzw for a DMU reset? i'm not sure what that is....and would vzw do a phone replacement??? they won't say it was voided?
Thanks all for all your help...i haven't had a chance to reflash anything yet, but gonna give it a go later today and pray it works!
Click to expand...
Click to collapse
if you call verizon, youre gunna have to make it sound like you know WAY more than they do about the issue. if you google 'DMU reset', im sure youll find some information about this. if you have another phone, switch your service to the other ESN, then switch it back. then call verizon and say that your MIP settings are not receiving a static IP from verizon. tell them you just switched your service back to this phone, and youve had this issue before. Tell them you need the data features removed and re-added to the account, and you need your DMU keys reset.
if you cant switch ESNs to and back, youll have to say you had a serious software issue on your phone, which required a hard reset and now your data connection is taking way longer than normal to connect, and you would like your DMU keys reset.
i recommend researching as much as you can about this before calling. depending on the TSR you get, they could ask you alot of questions. most of the time, if you answer all their questions before they ask them, theyll do what you say
EDIT:
when you do talk to them, before they can tell you any steps, make sure you tell them that you've:
soft reset
hard reset
clear storage
*288 1
*228 2
*22899
those are all the general things theyre gunna tell you to do before they reset anything for you. you just need to make it sound like youve already done everything possible, so the last possible step is resetting your keys for you
VZW has....well, an interesting way of doing things
So, I spoke to a VZW rep tonight after flashing back to a stock VZW ROM and, as expected, not getting a data connection (or able to make calls).
The rep was pretty helpful and knowledgeable. Mind you, i am on AT&T and this is my mom's phone i am helping her with (or at least trying to ). ATT base reps suck and for any minor network thing i would always need to speak to a data support tech (who these days tend to also suck pretty bad as well!) This VZW rep was no dummy and, to my surprise, understood all the things i threw at her. She was overly diligent which gets annoying, retrying lots of the same things, but i understand these people need to be, and she was making progress (bc after flashing the stock ROM my voice calling wasn't working initially either).
When I mentioned doing a DMU reset she explained that she can't do that and in order to have that done she needs to submit a request to her network team. I thought she would have them call me to troubleshoot the problem or something, but that isn't how it works . The network team doesn't speak to customers; she would be calling me back to tell me that the problem should be fixed and they did what they needed to do. I found it odd that they wouldn't need to speak to me to find out if it is working or not....Apparently, she said, they can tell if my phone is working/not working for the data connection.
For now i am kind of impressed with VZW's whole approach on how to solve this kind of thing (although it'd been nice if i coulda spoke NOW to a rep that can actually fix my problem), but i am a bit skeptical that it is actually gonna happen. We'll see what they come back with and hopefully i don't get run around in circles and they can indeed get my data working by resetting the DMU or whatever they need to do.
So, I spoke to a VZW rep tonight after flashing back to a stock VZW ROM and, as expected, not getting a data connection (or able to make calls).
The rep was pretty helpful and knowledgeable. Mind you, i am on AT&T and this is my mom's phone i am helping her with (or at least trying to ). ATT base reps suck and for any minor network thing i would always need to speak to a data support tech (who these days tend to also suck pretty bad as well!) This VZW rep was no dummy and, to my surprise, understood all the things i threw at her. She was overly diligent which gets annoying, retrying lots of the same things, but i understand these people need to be, and she was making progress (bc after flashing the stock ROM my voice calling wasn't working initially either).
When I mentioned doing a DMU reset she explained that she can't do that and in order to have that done she needs to submit a request to her network team. I thought she would have them call me to troubleshoot the problem or something, but that isn't how it works . The network team doesn't speak to customers; she would be calling me back to tell me that the problem should be fixed and they did what they needed to do. I found it odd that they wouldn't need to speak to me to find out if it is working or not....Apparently, she said, they can tell if my phone is working/not working for the data connection.
For now i am kind of impressed with VZW's whole approach on how to solve this kind of thing (although it'd been nice if i coulda spoke NOW to a rep that can actually fix my problem), but i am a bit skeptical that it is actually gonna happen. We'll see what they come back with and hopefully i don't get run around in circles and they can indeed get my data working by resetting the DMU or whatever they need to do.
Click to expand...
Click to collapse
She could have performed the DMU reset without bringing in the network team. She just didn't know how.
oh. well, for what it's worth, your support reps (even the bad ones apparantly) for the most part seem way better than the ones @ ATT! still not planning on switching any time soon though
Thank you!
I just want to deeply thank everyone that contributed to helping me get my problem fixed. The phone is now up and running and I am most appreciative to all of you that took the time to help me!!!
You really have a great community here!
FWIW, Verizon data tech fixed my problem but when i asked what he did he would not tell me....he basically said he "checked some things out and madde sure everything was set up right" while he had me take out my battery and wait. I asked what specifically he did, for research purposes and he said he couldn't tell me
Lol..he performed a DMU reset. I swear some of those techs are so dumb.
Well, he actually denied that he did a DMU reset cause i asked if that was specifically what he did and he said, no...i just checked some things out...and wouldn't tell me what he did.
i am sure you're right, he did the reset, but they must be instructed not to tell customers what they do...i guess maybe to try to prevent us from telling them what to do?
I was wondering if anyone else has seen this behavior.
The phones appeared to have the original VZW roms on them but I admit I didn't look as closely as I should have and write down the numbers.
I've two warranty replaced phones that work this way.
1. Flash olipro&latest radio & latest (4.1) DCD rom
2. *228 (succesfully)
(Thinking back, the first time I did this I *228ed before applying the carrier rom)
3. After that calls cannot be made EVERY call even *228 results in a roaming "call lost"
I can flash back the original signed VZW rom that was posted here a while back and restore phone operations.
The *228 update then worked but could not check messages. The switch to non-broadband phone and back to the titan got me able to check voicemail successfully. I've redone the cycle but after applying the DCD rom, it doesn't take me back to a phone needs initial programming state. I'm gonna try to go full circle a third time now and see if I missed anything when it was 2am.
*ADDITIONAL: I just realized that when power is hit or the phone battery saves to power off, it locks up. Even though the lights still blink.
Do you have any thoughts? Have you seen this before?
I'm tempted to install the latest from HTC, but I don't want to give up on GPS - or has it the recovery from that been proven now?
Status update!
I had also noticed that there was a 2mo newer carrier cab from DCD. That didn't help.
At this point I've up/down/crossgraded to MR2 successfully.
This resolved the lockup problem.
I am in the process of following this thread to resolve the GPS issues. Hopefully the new roms will work with this radio http://forum.xda-developers.com/showthread.php?t=481750
A work around
Ok I went through that whole process to no avail.
However, I found a solution that I REALLY dislike and you will too once I tell you what it is.
It seemed pretty obvious that vzw somehow flagged the phone during the upgrade process to disable it. This was perhaps because I hadn't loaded the carrier cab when I updated, though I've done that before on earlier without any lasting effect.
**** NOTE *****
I strongly discourage you from taking the steps I have done below. Done incorrectly, you are committing a prosecutable crime with jail time involved.
**** NOTE *****
Knowing calls were blocked and that I would have a chance to hit hangup before the call was actually placed (that's why it beeps) I dialed 911 hit send and hit hangup. Obviously the call did not even start because the phone was in lock down mode (I haven't mentioned this before but the phone always booted to the extended network.) when the call was attempted. However, Verizon is also obligated to process all 911 calls. So, it switched from extended, to roaming, to Verizon. The call had been canceled even before it got to roaming, so there was no contact with emergency services. The upside is that the phone is now on the Verizon Network with the new radio and new ROM. I can do everything except a *228. This includes checking voicemail, #768, rebooting etc. I've not tried a hard reset, nor do I think I will.
I REALLY don't like the method, but I have my phone back.
I'm traveling to TX next week for SxSW again. I may see if I can do a *228 from there and get a better result.
I just got done SBF'ing my phone (DX2) from the Atrix ROM because I didn't know about A-Key's and thought I lost something major. Anyway, I still plan on running a custom ROM but does anyone know if Verizon could detect that by chance when I call to get my phone re-authenticated? I don't want to call them twice in a matter of an hour or so.
AFAIK VZW cannot tell the difference. Furthermore, I don't think they care how many times you *228, as I've done it multiple times over the past week or so, and I know my friends done it a couple of times in an hour when he was first starting out with his DX. VZWs primary concern is that your MEID matches what they have on record, and isn't reported as stolen. They only really care if you have a custom rom on your phone if you take it in for repairs.
Ok, thanks. Just to clarify I'm not doing the *228 activation. It's activated and I can text, browse, etc. but I cannot place calls because my A-Key was wiped somewhere along the line. I have to dial #8899 and actually speak with someone. That's where I'm concerned about whether or not they will be able to detect the ROM and in turn void my warranty.
I don't believe they'll be able to detect the ROM, but have you tried *228? I just don't understand why you would have texting/data but not voice.
Yes I have done *228 twice. The problem is that the A-key (authentication key) was lost during one of the hard resets. I'm not sure why it happens but it does. I'm also not sure how you retain texting/data but lose voice. Here the thread I found that has a little more detail and the solution to the authentication problem:
http://forum.xda-developers.com/showthread.php?t=363967
Reading through that thread it doesn't seem like getting the A-Key would create any complications. Those people were in the same situation as you, and if they wanna know why you had a problem, then you had to hard reset, after installing some wonky programs cuz you're a dev.