Related
I've tried multiple times in different manners and cannot seem to get this command to work. At first I thought it might just be the DCD ROM I'm running but I even tried after flashing back the OEM. Actually flashed back just to see. So anyway, anyone else got any good ideas?
Now in my venture with ROM's yesterday and the new SPL I did end up messing my radio settings up. I figured if I just done *228 I could recover everything. Even though it said programming complete when I went to place a test call it said it couldn't authorize and told me to call *8899. I told the person who answered that I had to hard reset and now it wouldn't authorize. Then he asked me to *228 and I told him I already have with no results. He said do it again because he just reset something.
So once again I'm scratching my friggin head bacause of all of this. I can't get the commands to work so I can retrieve the A-Key and other info. Now I wonder if you can even get to that with Verizon in my area (Charlotte NC).
Anyone able to make sense of all of this and possibly lead me in the right direction?
try ##778
and then go to EDIT
the password you'll need is 000000 (six zero's)
coffey_joshua said:
try ##778
and then go to EDIT
the password you'll need is 000000 (six zero's)
Click to expand...
Click to collapse
I should have mentioned I tried that too
i'm in greensboro
and i've
dialed ##778 and then hit call and it brings you to the EPST screen
lllboredlll said:
I should have mentioned I tried that too
Click to expand...
Click to collapse
Use file explorer to browse to the windows folder on your phone. In there you will find an application called EPST. Open that up.
ryotgz said:
Use file explorer to browse to the windows folder on your phone. In there you will find an application called EPST. Open that up.
Click to expand...
Click to collapse
Finally Thaaaaaaannnnnnnnkkkkkkkkk you
Just followed your instructions, and run EPST ... is it normal that I don't have any A-KEY data
I'm on TELUS if that helps.
EPST is not working for me either. I got EPST Lab to fire up but nothing else.
Juicy47 said:
Just followed your instructions, and run EPST ... is it normal that I don't have any A-KEY data
I'm on TELUS if that helps.
Click to expand...
Click to collapse
Yes that is normal on Telus.
jjlwork said:
Yes that is normal on Telus.
Click to expand...
Click to collapse
So do I just not have an A-Key and ignore having to write this down prior to the flash?
Juicy47 said:
So do I just not have an A-Key and ignore having to write this down prior to the flash?
Click to expand...
Click to collapse
yes that's fine.
I actually am on Verizon in Chicago and do not have an A-Key....should I worry or does it only matter by location?
I have Verizon in San Diego. I managed to brick the phone. VZN support figured out that I'd somehow erased the A-key and gave me a new one. I noticed after entering it and going back to look at it that it couldn't be viewed (kind of like a password). On other occasions I've managed to get myself dropped from the local switch (there words - not sure what it actually means) and have my ESN erased from their system.
I've found that turning off the phone radio (put it in flight mode) before experimenting with it keeps it from mucking up the network and eliminates those late-night calls to tech support.
MoonlightRob said:
I have Verizon in San Diego. I managed to brick the phone. VZN support figured out that I'd somehow erased the A-key and gave me a new one. I noticed after entering it and going back to look at it that it couldn't be viewed (kind of like a password). On other occasions I've managed to get myself dropped from the local switch (there words - not sure what it actually means) and have my ESN erased from their system.
I've found that turning off the phone radio (put it in flight mode) before experimenting with it keeps it from mucking up the network and eliminates those late-night calls to tech support.
Click to expand...
Click to collapse
Moonlight,
Are you saying that by going into flight mode before flashing helps prevent losing your A-Key?
jeep14 said:
I actually am on Verizon in Chicago and do not have an A-Key....should I worry or does it only matter by location?
Click to expand...
Click to collapse
I am verizon in chicago and i didn't have an A-Key either. It didn't matter, i ended up having to call verizon anyway and i was talking to tech support for a good hour or two and they kept remotely trying to re-authenticate my phone... on the third try it worked.
They even gave me a new A-Key and the damn A-Key didn't even work... the operator said that was the first time she has ever seen an A-Key not work.
... anyway it is all working great after tech support helped me re-activate everything.
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.
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!
I would prefer this thread not become a "I am getting XYZ HELP!" thread, because it would be off topic. But I know it runs the risk of that because I would like to talk about the choice of Roms that XV6800 owners have used and the pros and cons of them.
I'm pretty sure I've seen the following GPS enabled ROMS on the verizon phones: (in order of complexity)
1. Original leaked ROM
2. No2Chem's nueROM http://forum.ppcgeeks.com/showthread.php?t=17219
3. DCD's 2.3.2 http://forum.xda-developers.com/showthread.php?t=371314
4. nexvisions's http://forum.xda-developers.com/showthread.php?t=364043
This section is now expanded to include a longer list of relative information needed to prepair for this process:
I've seen the Easy update thread: (This thread flashes the unlocker and radio in a single step using a ROM installation designed ONLY for a Sprint phone. Some believe this is why ppl have the 15 minute delay before aquiring a signal.)
http://forum.ppcgeeks.com/showthread.phpHere ?t=17667
You can see documentation for DCD's update from a Verizon Customer here:
http://forum.xda-developers.com/showpost.php?p=1973238&postcount=536
Here are the stock roms for recovery purposes (Signed and sealed by Verizon -not rips)
http://forum.xda-developers.com/showpost.php?p=1845171&postcount=13
Here is an unlocker: (also includes exit bl; read the .bat file to learn a lot and get some useful CLI commands)
http://forum.ppcgeeks.com/showthread.php?t=9093
Here is the Titan relocker:
http://forum.ppcgeeks.com/showthread.php?p=125160
Radio ROM 3.27.00
http://forum.xda-developers.com/showthread.php?t=362563
"general flashing rule is to start device in bootloader mode first and then flash. Do NOT flash it while it is running WindowsMobile OS."
Here are the generic steps to peform a standard burn from stock (works for some but all numbers should be written down in preparation)
0. WRITE DOWN ALL INFO UNDER ##778
0.1 REMOVE YOUR MicroSD CARD NOW!!!
1. Flash 2.40 unlocker using the Titanunlocker.bat inside the rar file (all files should be extracted to a new directory)
2. Flash DCD 2.3.2 (or preferred rom) different roms will
3. Flash radio 3.27
4. after booting dial a *228 to get the latest programing
That's it. It should be that simple.
If you are stuck, you might just be in the boot loader, use this tool for Verizon phones only to exit the boot loader:
http://forum.ppcgeeks.com/showthread.php?t=9229
Here's how to recover when it is not:
1. Using a PC, format a microSD card to FAT32.
2. Using winrar or an unzipper, extract the *.nbh file from the ROM upgrade .exe.
3. Copy the *.nbh file to the formatted microSD card
4. Rename the file on the microSD card TITAIMG.nbh.
5. Insert the microSD card into the phone and reset into bootloader.
6. The phone will tell you to press the power button to flash the ROM; do so.
Going into bootloader mode: power, camera, reset all at once.
Hard reset: Press the two dot (bottom menu) keys and hit the reset button, release all after two seconds. (RUMOR: Leaving the SD card in the phone may result in the SD card content being wiped. I don't care to test the rumor.)
I've read loads of threads tonight. My problem is that most of this stuff is slanted to Sprint stuff. I'm creating this as a central place for Verizon update facts. I'd love to hear if things work or if things don't work.
I'm considering flashing my phone tomorrow, (didn't happen yet by choice) but will also be travelling starting that night. Obviously the smart thing to do would be do go without GPS on my adventures, but it would be soo cool to have it working for SxSW just for the geek factor. And that calls to me.
So, here are some of my myths and mythunderstandings:
1. Every Verizon customer who updates their radio has to call into verizon to re-authenticate their phone. But Verizon is pretty cool about that even if you say you were flashing your phone.
2. This is true even if you follow the steps in the easy guide and write everything down it tells you to write down because Verizon uses a GUID generated by the radio rom when it is used for the first time on your phone. Not all areas as of today not every area does this but most and soon all will. It depends upon where you are in their upgrade chains.
3. If you install Radio 3.27, you're a screwed verizon customer because resets (hard and soft) and power ons (?????) will no longer aquire a signal right away. You will be waiting for 15 minutes or longer before you can use your phone again and no one has a working solution to this for Verizon customers. This happens to EVERY verizon customer.
4. People have upgraded to the original leaked rom without a problem (and without that delay) and that allowed them to have working phones possibly because of one or all of the following:
a. It is signed by Verizon and you don't have to unlock your phone?
b. MAYBE it doesn't require the radio upgrade???? (FIRST REPLY STATES THE RADIO IS REQUIRED FOR ALL GPS ROMS)
c. Because it was built using only Verizon stuff it is missing whatever incompatible tool the other kitchens have in them????
d. Because it has WM 6.0 and 6.1 hasn't been tested with Verizon????
5. DCD's rom has all of the MS Office software as an installable option whereas No2Chem's excludes it. Don't know if this includes outlook or not.
6. Both of the Kitchens mentioned above will work with Verizon and they have options that allow you to choose Verizon as an install option branding your phone correctly.
So that is upgrading your verizon phone as I understand it. Am I off too far on anything? I've not seen reports of any bricks yet but I know that is always possible.
So who has tried what ROM and to what degree of success?
BrianLayman said:
I would prefer this thread not become a "I am getting XYZ HELP!" thread, because it would be off topic. But I know it runs the risk of that because I would like to talk about the choice of Roms that XV6800 owners have used and the pros and cons of them.
I'm pretty sure I've seen the following GPS enabled ROMS on the verizon phones:
1. Original leaked ROM
2. DCD 2.3.2 with 3.27 Radio upgrade
3. No2Chem
I've also seen the Easy update thread:
http://forum.ppcgeeks.com/showthread.php?t=17667
You can see documentation for DCD's update from a Verizon Customer here:
http://forum.xda-developers.com/showpost.php?p=1973238&postcount=536
I've read loads of threads tonight and my problem is that most of this stuff is slanted to Sprint stuff. I'm creating this as a central place for Verizon update facts. I'd love to hear if things work or if things don't work. I'm considering flashing my phone tomorrow, but will also be travelling starting that night. Obviously the smart thing to do would be do go without GPS on my adventures, but it would be soo cool to have it working for SxSW just for the geek factor and that calls to me.
So, here are some of my myths and mythunderstandings:
1. Everyone Verizon customer has to call into verizon to re-authenticate their phone. But Verizon is pretty cool about that even if you say you were flashing your phone.
2. This is true even if you follow the steps in the easy guide and write everything down it tells you to write down because Verizon uses a GUID generated by the radio rom when it is used for the first time on your phone. Not all areas as of today not every area does this but most and soon all will. It depends upon where you are in their upgrade chains.
3. If you install Radio 3.27, you're a screwed verizon customer because resets (hard and soft) and power ons (?????) will no longer aquire a signal right away. You will be waiting for 15 minutes or longer before you can use your phone again and no one has a working solution to this for Verizon customers. This happens to EVERY verizon customer.
4. People have upgraded to the original leaked rom without a problem (and without that delay) and that allowed them to have working phones possibly because of one or all of the following:
a. It is signed by Verizon and you don't have to unlock your phone?
b. MAYBE it doesn't require the radio upgrade????
c. Because it was built using only Verizon stuff it is missing whatever incompatible tool the other kitchens have in them????
d. Because it has WM 6.0 and 6.1 hasn't been tested with Verizon????
5. DCD's rom has all of the MS Office software as an installable option whereas No2Chem's excludes it. Don't know if this includes outlook or not.
6. Both of the Kitchens mentioned above will work with Verizon and they have options that allow you to choose Verizon as an install option branding your phone correctly.
So that is upgrading your verizon phone as I understand it. Am I off too far on anything? I've not seen reports of any bricks yet but I know that is always possible.
So who has tried what ROM and to what degree of success?
Click to expand...
Click to collapse
1. There are people who say they did not need to call verizon, but i did.
2. this is mostly true, some areas still use an akey but verizon will gladly give that to you, just tell them you did a hard reset.
3. the roms that work with GPS require the 3.27 radio... I had no delay with using the phone after any flash (i've done several) there is a delay for GPS to work the first time
4.a. original leaked rom was from sprint
4.b. the radio upgrade to 3.27 is required or GPS will not work and neither will any rom that is based on this radio
4.c. again original leaked rom is from sprint and contains no verizon stuff, dcd broke down the leaked rom and made available to everyone else
4.d. the titan or xv6800 shipped with 6.0 (6.1 to release soon for verizon, although i have it now)
5. the outlook portion of office is standard on all pocket pc phone
6. True...you must choose your carrier or you won't be able to connect to your towers properly
that being said, I use a rom built with dcd's kitchen and am very pleased, if you want one with lots of stuff you may want to try nexvisions rom
Hope this helps
rmancl said:
that being said, I use a rom built with dcd's kitchen and am very pleased, if you want one with lots of stuff you may want to try nexvisions rom
Hope this helps
Click to expand...
Click to collapse
Thanks rmacl! That helps a lot. Reading through a few hundred pages of facts for different versions mixed in with cries for help and resolved issues can make the process, for someone who thought a kitchen was a room till a very short time ago, pretty daunting no matter how tech savy they are they are.
I appreciate your help in solidifying the details.
I will then be upgrading my phone tomorrow. I plan on following the easy update post listed above exactly as it is written.
I saw one post of a person who had done the same thing EXCEPT that they took a break and installed SPL 2.40-olipro. They had the 15 minute pause in aquiring the signal. So, I am wondering if that is a contributing factor. I'm thinking that the "Sprint unofficial 3.16 Release" includes an upgraded boot the spl/bootloader.
If this is a bad plan, or if it is not how you did it successfully and you are willing to share the steps you followed, please let me know.
Thanks again for your help.
EDIT: nexvisions rom pretty closely matches my current config. And what I don't have from that rom I like. The rest of the stuff I have installed should be enabled when I run a sprite backup restore. Thanks for the suggestion
Just did this today-
I'm using NexVision's Hybrid ROM(version based on dcd's latest 2.3.1).
I did the following:
1. Update SPL app
2. Loaded above ROM
3. Loaded latest radio
4. *228 'ed to get programming
5. did IOTA for some reason
6. No outgoing calls. Could not authenticate. Had to call VZW and they got me going in a few minutes. (the MSL for my phone i got from GetSPC.exe didn't work)
So, bottom line- My 6800 is working just fine with NexVisions Hybrid right now.
Anything else you'd like to know?
I was up and running on a DCD 2.3.2 cooked ROM and 3.27 radio with issues acquiring signal. Some have implied that running the "Easy Guide" instructions on PPCGeeks would resolve the delay in acquiring signal issues.
I couldn't get the leaked 3.16 ROM loaded using the 1.06 Bootloader, so I loaded the 2.40 Bootloader and then successfully loaded the leaked 3.16.
This put my phone on Sprint. According to the guide, running DCDs ROM that I cooked using the kitchen would reset the phone to Verizon (by selecting Verizon as my carrier.) This didn't work. Right now my phone is running the DCD ROM, 3.27 radio, and I can't get into the PST to edit the MSID and MDN.
Guess I'm going stock and upgrading again.
Am I the only one or is the fact that this phone is carried by at least 2.5(sorry alltell) major carriers a problem. We get people, admittedly I almost was one, that flash their phones with roms for the wrong carrier and then wonder what's going on. One would hope that you could pick up a cdma phone and use it on a CDMA network but that's just not true. There are tons of documented and undocumented crap holes that deviate from the spec because of the ad-hoc hobbled together system that is the United States cellular system. I would suggest splitting sprint and verizon but that would further fragment an already super fragmented market.
I am not sure the state of your phone or how to go about fixing it but the easy guide does seem to be for sprint users and not for Verizon. There is yet to be an uprgrade sanctioned for us - I hear it's coming, but I heard that with the Samsung i730 - and it took 9 months to get from 'soon' to released.
VX6800 DCD2.3.1 Working great
Ok I am an engineer on the network and perhaps Murphy got me to be over prepared and so I had the least problems. Started stock, flashed 2.40 unlocker, flashed DCD 2.3.1, flashed radio 3.27, booted back up and worked perfectly. I did write down everything, and I do mean everything that could be gotten in the PST ( by the way, the MSL on Verizon units is 000000 and no GetMSL is required) so I did not need that. I called VZW data support and told them that I was about to do a hard reset and had heard that sometimes the A key got messed up, so he gave it to me up front just in case, and because I had it ready is why I suppose I did not need it either. My signal came up perfectly, my PRL and provisioning data did need a *228 option 1 to get it back in, my GPS came right up fast and accurate, could make and receive calls right away, MMS worked perfectly right away. The only problem that I have with the new ROM is that the 'box type' mini-usb to 3.5 mm adapter with the mini-usb pass thru does not work properly anymore, but my stock one and my pigtail adapters do work, so it is somthing in the adapter design. Also SelectRadio 4.02 drops out as if the data connection goes down and back up, but it does not. I look at the PPP data and it is perfect, and when I just put my channels in Resco Pocket Radio all is well.
Well, I'm a long experienced IT guy with a background of working in cellular....so I'm not exactly ignorant on the subject.
madman, I did the exact steps you did, with the exception of writing down every setting in the PST (just the MSID and MDN). Yet my phone takes 15-20 minutes to acquire signal. Was there anything you had to adjust besides the MSID and the MDN?
To complete my story from my last post, I was able to recover back to a VZW stock ROM and try again. Second time around I didn't let the Sprint cutomizations run. That fixed the problem of my phone being "Sprintized". However, it didn't help with my issues acquiring signal (which was the entire reason I went through this exercise.) BLAH.
Having 1 set of instruction for Sprint and Verizon is fine, but what we need is are people from each side working together on the documentation. Right now everything seems to be completed by Sprint users.
Geckotek said:
...
To complete my story from my last post, I was able to recover back to a VZW stock ROM and try again. Second time around I didn't let the Sprint cutomizations run. That fixed the problem of my phone being "Sprintized". However, it didn't help with my issues acquiring signal (which was the entire reason I went through this exercise.) BLAH.
Having 1 set of instruction for Sprint and Verizon is fine, but what we need is are people from each side working together on the documentation. Right now everything seems to be completed by Sprint users.
Click to expand...
Click to collapse
I'm willing to bet it's the fact that you used a sprint rom. Even though it said you weren't sprintized I bet there are still sprint ghosts in your phone. These things aren't well documented nor are they straight forward. I am sure that there is something in the sprint rom that is causing your problem (it's the only thing that is different from stories of people who have been successful)
ICLKennyG said:
I'm willing to bet it's the fact that you used a sprint rom. Even though it said you weren't sprintized I bet there are still sprint ghosts in your phone. These things aren't well documented nor are they straight forward. I am sure that there is something in the sprint rom that is causing your problem (it's the only thing that is different from stories of people who have been successful)
Click to expand...
Click to collapse
Well, what you are saying is basically what I've suspected all along. I think the 3.27 radio is basically a rip from a Sprint ROM...right?
This is why I am trying to get a VZW tech to review ALL of the PST settings with me. She was gonna call back, but stupid me, I think I reset my phone and missed her call. Grrrrrr
Geckotek said:
Well, what you are saying is basically what I've suspected all along. I think the 3.27 radio is basically a rip from a Sprint ROM...right?
This is why I am trying to get a VZW tech to review ALL of the PST settings with me. She was gonna call back, but stupid me, I think I reset my phone and missed her call. Grrrrrr
Click to expand...
Click to collapse
What I am saying is the Sprint Rom is for Sprint. The radio is a radio from what I can tell. It doesn't seem to be setup to be one company or another with the correct rom. However what you are doing is taking a rom that is built by another carrier for their network and trying to use it on your network. Use a verizon intended rom (Hint: not sprint) and the 3.27 radio and you should be fine.
One would hope that you could just strip the sprint part out of their roms and run it on the VZW network but we all know these devices are more hodgepodge then strict implementation of standards.
ICLKennyG said:
What I am saying is the Sprint Rom is for Sprint. The radio is a radio from what I can tell. It doesn't seem to be setup to be one company or another with the correct rom. However what you are doing is taking a rom that is built by another carrier for their network and trying to use it on your network. Use a verizon intended rom (Hint: not sprint) and the 3.27 radio and you should be fine.
One would hope that you could just strip the sprint part out of their roms and run it on the VZW network but we all know these devices are more hodgepodge then strict implementation of standards.
Click to expand...
Click to collapse
There is no Verizon intended ROM that I'm aware of that supports the 3.27 radio.
spreeway said:
J
6. No outgoing calls. Could not authenticate. Had to call VZW and they got me going in a few minutes. (the MSL for my phone i got from GetSPC.exe didn't work)
Click to expand...
Click to collapse
getspc.exe is for sprint only
the msl code for verizon is "000000" minus the "'s
I've added a bunch of info to the first post. I haven't had time to do the flash till now. After I pack tomorrow, I should be able to do it. Plus I wanted to have all my ducks in a row for this process. I'm now fairly confident I know most of the failure points in the process and how to recover from them... we'll see.
Geckotek said:
There is no Verizon intended ROM that I'm aware of that supports the 3.27 radio.
Click to expand...
Click to collapse
Ummmmm NexVision IS a verizon user and his ROM is most certainly built for verizon above others, sprint and alltel second. DCD also has an option in his kitchen for verizon. as for No2Chem... I havnt used his rom so I couldnt tell you for sure. But I assure you as I am alive and breathing, there are ROMs intended for the Big Red V, I know I use one and Love it. I messed up when I first flashed, but never had to call VZW about it, just reflashed to stock then tried again.
As stated, I used both DCD and NexVision and both activated, called and surfed on the network. If you have any specific questions, I will gladly field them, Specialy since I have insurance on the phone... If it hoses, i will break and replace it.
Launching my first rom flashing...
blksprk said:
Ummmmm NexVision IS a verizon user and his ROM is most certainly built for verizon above others, sprint and alltel second. DCD also has an option in his kitchen for verizon. as for No2Chem... I havnt used his rom so I couldnt tell you for sure. But I assure you as I am alive and breathing, there are ROMs intended for the Big Red V, I know I use one and Love it. I messed up when I first flashed, but never had to call VZW about it, just reflashed to stock then tried again.
As stated, I used both DCD and NexVision and both activated, called and surfed on the network. If you have any specific questions, I will gladly field them, Specialy since I have insurance on the phone... If it hoses, i will break and replace it.
Click to expand...
Click to collapse
Ummmmmm, you completely missed the point.
So is there any word when Verizon will release an update similar to what we are able to do with the new ROMs and Radio?
I mean if it's going to be a month away, I may just, if it's going to be 3 months or forever then I guess I'll have to try it.
It seems either it works perfect, or it doesn't, and some people don't need to enter in an akey? Interesting...
I went from a stock XV6800 (Verizon) to the 2.40 unlocker, the 3.27 radio and a ROM built off of DCD's 2.3.2 kitchen. I did not need to record *any* of the phone's programming info. After flashing, *228 successfully set up the phone and I was able to start making/receiving calls.
"3. If you install Radio 3.27, you're a screwed verizon customer because resets (hard and soft) and power ons (?????) will no longer aquire a signal right away. You will be waiting for 15 minutes or longer before you can use your phone again and no one has a working solution to this for Verizon customers. This happens to EVERY verizon customer."
This seems not to be true, because I'm a Verizon customer and it didn't happen for me. I get both a cell and data signal right away on either reset (soft, anyway; haven't had to try hard yet) or power-on.
I'm a happy camper so far, with the only glitch being one unexplained soft reset one morning while the phone was waking up to execute an alarm. The phone reset instead and the alarm sounded when it came back up. Hasn't happened again since.
rmancl said:
getspc.exe is for sprint only...
Click to expand...
Click to collapse
No, I can verify that it works for Telus as well.
I have searched for hours and did not see anything that relates to my specific situation. I have the HTC PPC6800 via a small carrier/service provider with no “smart phone” tech support. They have been great and I’m not interested in changing. They have obviously purchased the 6800 through a large carrier. I would like to know if there is any way via a registry editor, software, etc., that I can find out which carrier (Alltel, Sprint, etc) my 6800’s software is based on so I might be able to upgrade. I’m running WM 6.0, the ROM is 2.17.557.0 and the Radio is 1.64.00.
Thanks!
2.17 sounds like first sprint rom..Is it cdma?
Yes it is CDMA.
Previously I did try to upgrade to the Sprint ROM off HTC's site and it was 2 days of "hair pulling" to get it back working again. There is nothing that displays, or can be found on the phone to indicate there is any specific carrier. I was hoping that somewhere there might be an "indicator" in as to which carrier it is based on.
Thank you for responding!
I believe the roms themselves are all generic to a point, the stuff that makes them carrier based is the apps they include and the stuff that the carrier cab installs on custom roms. I know the carriers don't use the same cabs we have, but I would imagine if you use QPST to read and save your programming configuration and then copy down every single line of info in your EPST and then double check your dial up connection, make sure it's #777 that it dials, that you should be able to flash any rom and then write back your info with QPST and then re-enter all the info from EPST, make sure your dialup connection is back, and this really should get you back up.
I don't really have a lot of info on carriers, but USCC is like yours they use someone elses work and just build off of it. So I don't have a stock carrier to revert back to as well.
I know I flashed someones phone the other day that I just could not get QPST to read the info from, and was able to get it back online by just writing back my QPST info from my phone and just edit the fields that were account specific and then fixed a couple lines in EPST and everything worked.
So I believe my method I described above should get you up and running, but I could be wrong, might want to wait until a couple other experts chime in.
BTC
BTC,
Thank you! I will give your instructions a try after doing lots of research!