Ran the Sprint ROM on my XV6800, now a mess - Mogul, XV6800 ROM Development

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!

Related

VZW users and A-Key problems, anyone found a good method?

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.

Preferred Roms for the XV6800

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.

Is it possible to start over on Verizon XV6800?

I cannot get my new phone to get a signal after the following:
1. 2.4 unlocker (Hard-spl-mfg.exe)
2. Sprint Rom (RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship.exe)
3. DCD Rom (DCD_3.0.1_Verizon.exe)
I believe I followed all of the instructions and upgraded my XV6800 from stock to DCD 3.01. When I finally get booted up I can never get a signal acquired. I can dial *22802 and let it connect and then I get a signal, but even then I get an error about the #777 internet access, so something is wrong. I new A-Keys and made sure all of my info was written down and correct.
Is there a way to start over from stock? Can I relock and put the stock Verizon on and try again?
Help!
did you.....
When you ran in the Sprint ROM did you let the customization run ? If so then there is the problem, as it overwrites verizon parms with the sprint. That can be fixed by getting the VZW PRL and running it in with the EPST, then set your home SID/NID also in EPST, then you should have VZW signal and not roaming, then a *228 should reprovision the rest. If you did not write down your info before you flashed then you missed a step.
I was under the assumption that the Sprint customizations don't run until I tap the welcome screen which I did not. I immediately installed DCD 3.01. I'm returning it to stock to see if I can get a signal then starting over.
Where can I get the VZW PRL? I will search now.
ok then they did not run
well I guess they did not run but maybe your PRL and provisioning data got wiped, MSID, MID, SID/NID, you know that stuff. There are stock VZW ROM images out there but my methode would fix it safer and easier as I am sure that the signal issue is a missing or wrong PRL. Go into EPST (##778) and select 'view' and then look at PRL which should show 50989 or somthing close as that is the current VZW PRL, a different number would be someone elses overwritten on yours, blank is no PRL which is also badd. then look at SID/NID where the first set should be populated. If you fix just these 2 things then you should get back on VZW signal and be able to provision it. Going with a full restore is like crushing and reconstituting your car when it only needs a wash and the ash trays emptied. If you do still want to though, the stock images do exist here.
I relocked and put the Verizon stock back on and went through the setup procedures and the phone works great back at stock.
I started the update over.
Installed the Unlocker.
Installed Sprint ROM. No customizations allowed.
Installed DCD 3.01
Signal does not acquire but will after 15 minutes or so and all is fine. As soon as I soft-reset.. no signal. The PRL is the 50989 the latest. All of my MSID and other numbers match.
Maybe it's the DCD 3.01. I don't know where to find 3.0.0.
I'll keep searching. Thanks madman34 for your help!!!!
I've noticed that after waiting for the signal 15 minutes, everything works wonderfully. I've tried changing the MIP MODE over and over but that hasn't worked.
Anyone with DCD 3.01 and the new Sprint ROM Radio able to get a signal without waiting 15 minutes?
HELP!
Yep, I get signal within 3 seconds.... Not sure what the issue is with your phone....? I am currently a Verizon user....
I am a Verizon user with DCD's 3.0.1 and upon soft reset get a signal within 2-3 seconds.
Hi guys, just to let you know I'm in the same boat at the OP with a Verizon phone and No2Chem's 5055. I'll start a new thread with a more descriptive title and see if we can get some additional help.
KeithGP said:
I relocked and put the Verizon stock back on and went through the setup procedures and the phone works great back at stock.
I started the update over.
Installed the Unlocker.
Installed Sprint ROM. No customizations allowed.
Installed DCD 3.01
Signal does not acquire but will after 15 minutes or so and all is fine. As soon as I soft-reset.. no signal. The PRL is the 50989 the latest. All of my MSID and other numbers match.
Maybe it's the DCD 3.01. I don't know where to find 3.0.0.
I'll keep searching. Thanks madman34 for your help!!!!
Click to expand...
Click to collapse
Did you try the *22802 and hanging up? Geckotek mentioned that as a fix to the problem.
I also found that the customizations tried to run after installing DCD 3.0.1, did you let those run?
Osteo said:
Hi guys, just to let you know I'm in the same boat at the OP with a Verizon phone and No2Chem's 5055. I'll start a new thread with a more descriptive title and see if we can get some additional help.
Click to expand...
Click to collapse
What city do you have service in?
I did try the *28802 and it didn't fix it for the N2C rom. Man, I'm getting depressed over this.... I'm in middle Tennessee (Cookeville), great cell coverage for both Sprint and Verizon.
Osteo said:
I did try the *28802 and it didn't fix it for the N2C rom. Man, I'm getting depressed over this.... I'm in middle Tennessee (Cookeville), great cell coverage for both Sprint and Verizon.
Click to expand...
Click to collapse
is your PRL 50989?
http://www.corolada.com/prl/
lllboredlll said:
is your PRL 50989?
http://www.corolada.com/prl/
Click to expand...
Click to collapse
I've gone back to stock so that's what it says now. During my 1st call to tech support they had me go over many of the EPST settings and I think that's what it said but I was so perturbed I don't recall. I'll try again (was thinking of trying DCD's most recent as he has carrier specific ROM's) and if I loose the radio, I'll check again. Thanks for the input....
Is the fundamental issue here that your installing a SPRINT rom on a VERIZON VX6800?
Why not try installing a VERIZON rom?
spreeway said:
Why not try installing a VERIZON rom?
Click to expand...
Click to collapse
If I wait for VZ to release a WM6.1 ROM with GPS I could be old and gray... I'll try DCD's most recent with VZ ROM and Sprint Radio tomorrow...
spreeway said:
Is the fundamental issue here that your installing a SPRINT rom on a VERIZON VX6800?
Why not try installing a VERIZON rom?
Click to expand...
Click to collapse
Spreeway, there is no such creature that enables RevA and GPS. These are enable by using the new sprint ROM (to upgrade the radio) and then a custom rom (DCD!) for verizon.
Quick update. Resolved. It was a prl issue, rolled back to an older prl and all is well. I guess I'll have to wait for an official rom from VZW to get the latest prl but all is working now.... How odd.
I am using 50989 with 3.0.1. Now that you're back to an older prl, dial *228 NOT *22802 and then press 2 at the prompt. Update the prl OTA and see if it works this time.
Tried and failed... Yesterday, once I figured out about the older PRL, I upgraded and called for a new A key. Tech support updated the A key on their side and he had me run *228 option one and when it rebooted I had no signal. I checked the PRL and it was 51020! They must have just released a new one... Rolled back with the tech on the line, didn't need a new A key and all is well since.
I still can't figure out why any of the Nationwide PRL's drop my signal but as my plan has coast to coast no roaming, I think if I get outside of my home zone it should still pick up towers (I hope but I dont travel much).
Also, I can't figure out why I can't change the roaming options in the phone options. It currently has no check infront of 'Sprint only' or 'roam only' and if I check either I loose the cell radio. Very odd!

Flashed DCD 3.2.2 and can't access internet, also showing Sprint info instead of VZW

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?

Diagnostic help on Refurb phone - Will only dial from vzw signed roms

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.

Categories

Resources