View Full Version : VX6800/Mogul/Titan "Network Connection" Issues
Sandy Korda
06-06-2008, 08:15 PM
As many of you who have followed my previous rants already know, I recently upgraded from an out-of-the-box unit to a GPS enabled device - via a sampling of the 3.35+ Radio and the 5060+ ROMS - and have MAJOR problems when trying to access a non-WiFi internet, SMS or email connection - via Network Connection.
Although my PHONE continued to work fine, and I could send and receive instant Text messages... I could NOT send or receive ANY MMS or SMS transmittals. I could, however, access my email and the internet - via WiFi (at first), but - when I attempted to connect to same via Verizon Wireless... my Verizon VX6800 starts to connect via the #777 access, but will show an empty Password box on the Network Log On page (in other words it doesn't save the Password from a previous attempt - even after I type "vzw" and check the box).
At first - we were receiving error messages that said: "Error Code 11; PPP Connection Error" and "Network Connection Failure".
I can not begin to tell you how many times we took the battery out and did hard resets... as well as dialed "*228"...! I've even returned the device back to the original settings (ROM 2.09.605.8; Radio: 1.30.60) and - with the exception of the "Error Code 11" and PPP message... STILL have these connection issues.
Countless calls to Tech Support have finally put me in touch with one Ian Chamberlain... a most sincerely concerned, patient and articulate tech dude... who went the extra mile, and then some, to troubleshoot the problem. Yes, (as with all the others) he knew from the start that I had cracked the OS and upgraded from 6.0 to the much more desired 6.1 - with the needed GPS... and he STILL was willing to try to help.
In the course of his investigation, we discovered (much like that of a few fellow XDA-Dev'ers & PPCGeekers) that there was a Network setting (on Verizon's end...) that somehow required "resetting". Foregive me, but I've forgotten just what it was called... a DMU setting... I believe. Anyway... once that was preformed, we no longer received the afore mentioned "Error Code 11, etc." message - and now ARE able to receive MMS messages... but, still are NOT able to send or receive email OR access the internet on anything other than WiFi. A direct EVDO connection takes us to the Logon to Server page.
Thinking it may NOT be just be this device, Verizon has kindly offered to send us a NEW, out-of-the-box device (rather than a referb unit)... knowing I'm going to attempt to upgrade it. The current belief is - that in addition to the Network Connection Switch issue, we previously may have unwittingly been given replacement phones (from our local Verizon Wireless store) that may have been part of a "bad batch".
Once the new unit arrives (sometime tomorrow) I'll try it "as is" - in it's natural form... both via WiFi as well as direct - with a Network connection. If that works without flaw, as hoped, then we'll attempt to upgrade to the 2.40 boot loader, then the more stable 3.35+ Radio and N2C 5060 ROM... (that is, unless any of you have a better, more reliable suggestion).
Has anyone else had similar connection issues...? ANY helpful insight would be MOST welcomed, not just by me... but by many fellow VX6800/Mogul/Titan users, as well.
More to follow.
__________________
Sandy Korda
Firefighter/EMT,
Accountability, Incident Management & Disaster Mitigation Specialist
FIRE-RESCUE PRODUCTS, INTERNATIONAL
a division of The Image Group, Inc.
www.image911.com
When you initially upgraded to 3.35, did you let the Sprint customizations run by accident?
Sandy Korda
06-06-2008, 09:15 PM
Negative. I pushed my stylus into the reset port prior to the Custom Install 3-2-1- count down.
You would benefit by following my handy tip here:
http://forum.xda-developers.com/showpost.php?p=2212691&postcount=336
Search is your friend, and takes less time than ranting. Cheers!
Negative. I pushed my stylus into the reset port prior to the Custom Install 3-2-1- count down.
We are aware of the DMU public key issue. It usually gets wiped when people who are not Sprint users have updated their PRI to Sprint's 2.03 PRI (part of customizations). When you flashed back to stock, RadioRefurbish.sa.cab was installed as part of Verizon's customizations reverting you back to the Verizon PRI, though it clears the DMU public key in EPST. The DMU public key, located in EPST under M.IP Default Profile, is a public key which authenticates to Verizon's AAA server upon connecting to #777, and writes the AAA Shared Secret and HA Shared Secret private encrypted keys in EPST also under M.IP Default Profile.
Go into EPST by dialing ##778, choose Edit, enter SPC 000000, and then select M.IP Default Profile. There should be encrypted values in those 3 fields. Are they blank? If so, the DMU reset did not work. Also check the HDR AN AUTH Password field under the Security tab in EPST. That too should have an encrypted value. If it's blank too, the DMU public key still hasn't been reset.
You can manually reset the DMU public key, but can't through EPST. QPST must be used with the phone in DMR to write the key to the proper directory.
You would benefit by following my handy tip here:
http://forum.xda-developers.com/show...&postcount=336
Search is your friend, and takes less time than ranting. Cheers!
This is incorrect. The Verizon carrier cab does not write EPST values, nor does it reset the DMU public key.
.....
This is incorrect. The Verizon carrier cab does not write EPST values, nor does it reset the DMU public key.
Since its worked for me over a dozen times, I guess you are correct and know more than anyone else. Give it a rest!
Sandy Korda
06-06-2008, 10:36 PM
Perhaps... but, we were having the Data Connection Error along with the repeated missing Password issue even AFTER we upgraded (and before we went back to the OEM settings).
Since going back to the original format, we even attempted to connect after adding a new modem connection... with no luck.
I ##778'ed and made the changes to the settings, saved, reset and STILL - the problems persisted.
I'll share your comments with the service tech.
dcd1182
06-06-2008, 11:36 PM
Since its worked for me over a dozen times, I guess you are correct and know more than anyone else. Give it a rest!
maybe you guys mean 2 different things. the verizon cab sets up ##PST(send) shortcut to launch EPST.
it does not write any values accessed via EPST, it does not run radiorefurbish, it does not load PRI, and it does not touch DMU key, HA, AAA, etc.
Perhaps... but, we were having the Data Connection Error along with the repeated missing Password issue even AFTER we upgraded (and before we went back to the OEM settings).
Since going back to the original format, we even attempted to connect after adding a new modem connection... with no luck.
I ##778'ed and made the changes to the settings, saved, reset and STILL - the problems persisted.
I'll share your comments with the service tech.
well, obviously your problem lies within non volatile provisioning as it carries over between flashes.
i think your answer lies in gcincotta's previous post. the dmu reset maybe did not really take.
Go into EPST by dialing ##778, choose Edit, enter SPC 000000, and then select M.IP Default Profile. There should be encrypted values in those 3 fields. Are they blank? If so, the DMU reset did not work. Also check the HDR AN AUTH Password field under the Security tab in EPST. That too should have an encrypted value. If it's blank too, the DMU public key still hasn't been reset.
Sandy Korda
06-06-2008, 11:50 PM
Actually, as I posted my comment from work... and had to attend to some other matters, I had no idea anyone had replied as quickly to my posting! I was late in responding in a rapid fashion to Gcincotta's missive. (Someone beat me to it.) My comment was NOT meant as a slighted response to Ebb's observant perspective... regardless of how it may read. Out of context, it presents as such, yet - I never intended my utterances to ever have been disrespectful.
My sincere apologies if they were.
dcd1182
07-06-2008, 12:53 AM
Actually, as I posted my comment from work... and had to attend to some other matters, I had no idea anyone had replied as quickly to my posting! I was late in responding in a rapid fashion to Gcincotta's missive. (Someone beat me to it.) My comment was NOT meant as a slighted response to Ebb's observant perspective... regardless of how it may read. Out of context, it presents as such, yet - I never intended my utterances to ever have been disrespectful.
My sincere apologies if they were.
its all good i just want you to try what he posted :)
there are further steps that will restore your service if we know this is the problem..
Sandy Korda
07-06-2008, 01:18 AM
Quote:
Go into EPST by dialing ##778, choose Edit, enter SPC 000000, and then select M.IP Default Profile. There should be encrypted values in those 3 fields. Are they blank? If so, the DMU reset did not work. Also check the HDR AN AUTH Password field under the Security tab in EPST. That too should have an encrypted value. If it's blank too, the DMU public key still hasn't been reset.
__________________
Have done the above... and noticed that - according to your observations - the DMU must not be catching, as the HDR AN AUTH Password - under the Security option is STILL missing... as are TWO (not Three) fields under the M.I.P. Default Profile: HA Shared Secret and AAA Shared Secret... both of same are still blank.
According the Ian, the switch was reset yesterday - and the Network issue was believed to have been corrected - since we were then able to receive the MMS messages, when previously - we were not able to.
The same problem existed with the two previous devices - obtained from the same location... and could possibly be from the same production lot. If there were a production error, it is more than likely that it would/could have ended up in this group. The replacement device due in tomorrow is coming from a totally different location. If it is problem-free, it might suggest that this section of Vermont received a bad "batch".
Thusly, we're hoping the new unit may prove this theory out. If the new device should hold not only the password, but also be able to access thee internet and email via a network connection, as well as via WiFi, then we have a clean device to re-load the upgrade as you suggest.
~ Sandy
Have done the above... and noticed that - according to your observations - the DMU must not be catching, as the HDR AN AUTH Password - under the Security option is STILL missing... as are TWO (not Three) fields under the M.I.P. Default Profile: HA Shared Secret and AAA Shared Secret... both of same are still blank.
I'm sorry, I was at work when I first posted and didn't realize my error. The DMU public key shouldn't be blank, it should be set to 10, whether it was reset or not, it never goes away. However, you know you have a bad public key when it is not writing the HA Shared Secret, AAA Shared Secret, and HDR AN AUTH Password, as you've stated these are blank.
Thusly, we're hoping the new unit may prove this theory out. If the new device should hold not only the password, but also be able to access thee internet and email via a network connection, as well as via WiFi, then we have a clean device to re-load the upgrade as you suggest.
There is a way (through service programming) to manually reset your DMU public key. I see you're expecting a new device so hopefully that will fix your issue, as the DMU public key on it should be valid. Just for future reference though, WiFi is unaffected by DMU. I think you said in your original post that WiFi works but EVDO doesn't. That makes sense as the DMU public key is only needed to create a 3g connection via EVDO. WiFi doesn't connect via #777 and therefore needs no authentication.
Best of luck with the new device though, and keep us posted.
Sandy Korda
07-06-2008, 01:43 AM
The DMU public key (PKOID) IS set to "10" - as you just mentioned. The only items blank are the HA and AAA Shared Secrets. And, that of the HDR AN AUTH and PPP Passwords (under Security).
The DMU public key (PKOID) IS set to "10" - as you just mentioned. The only items blank are the HA and AAA Shared Secrets. And, that of the HDR AN AUTH and PPP Passwords (under Security).
Yup...dmu key isn't doing its job. It writes the PPP password as well, but I didn't bother including it in the post as that's only used for the older dial up data connection.
If your dmu key is properly reset on that device (or is healthy on your new device), those 4 fields should be filled with encrypted data.
MstaCDLite
09-06-2008, 05:24 PM
I am having similar issues with my phone. I checked the settings mentioned and my phone does have encrypted values in the fields. is there a resolution if the phone does have the encrypted passwords? My phone is running the same radio and rom.
I am having similar issues with my phone. I checked the settings mentioned and my phone does have encrypted values in the fields. is there a resolution if the phone does have the encrypted passwords? My phone is running the same radio and rom.
If your DMU key is writing the encrypted values, then it is not a DMU key issue.
My advice to you would be for you to *228 option 1, then try and connect. If it says check username and password, go into Connections and Manage Existing Connections, and manually put in your10digitphonenumber@vzw3g.com for username and vzw for password, leave domain blank, set it to save password, and try to connect again.
If this fails, it also could be an issue on their end. Sometimes Verizon's computers go funky and they need to remove the data package from your account and re-add it. So if the above 2 steps fail, call them and have them do that.
Sandy Korda
09-06-2008, 07:17 PM
As I mentioned in my original musing, a chap in the Tech Support department at Verizon's "Midnight Tech Crew" was MOST helpful when I first opened this forum. Ian Chamberlain (at Extension #2837) has been my "go to guy" of choice, as his old school commitment to customer service (satisfaction) is not only refreshing, but personally helpful as well...! That said, he not only assisted me in setting up my NEW (not refurbed) device, but also discovered (after doing some deep level research) that although another tech had made the usual switch flips, key punches and button pushes... something just wasn't Kosher... and took it upon himself to do it all over, once again. Wouldn't you know it - it made the difference! We even back tracked... and reactivated my original device - just to see if the settings were the actual culprit... and wouldn't you know it - it too was working good as new!
I'm sending the new unit back, as it wasn't needed, after all.
Talk about a Tech guy willing to stay with a customer until he (or she) is completely satisfied...!! When I offered to keep working WOW! I know Verizon is proactive to their customer's needs, but - this guy goes well beyond the usual call of duty. He even offered to stay with me while I upgraded my Radio, and installed the newest ROM... just to make sure everything was working to my satisfaction! Now, if ALL of Verizon's crew was like that... it in and of itself is enough of a reason to stay with the company!
Oh yeah, the service is right up there, too!
Yeah Sandy, the dmu key was probably not being reset correctly by the other rep. When Ian properly reset it, it worked fine.
I'm glad you got a rep that was willing to help so much...so far I haven't come in contact with anyone from VZW support like that.
Sandy Korda
09-06-2008, 07:52 PM
Ian and I were speculating that perhaps I was continually being given devices that were out of a "bad batch" and had some software issue in them... so he arranged to have a NEW device sent from another location (Texas)... for a NextDay/Saturday delivery! Serious bite of change to ensure customer satisfaction!
I know you're with "the Other company"... but, in all fairness, you too - have been equally as helpful - to many of us, as we attempt to not brick our devices in our valiant desires to upgrade and flash anew! Such levels of end-user dedication is not often seen nor experienced in the world of today's "Instant Gratification Generation".
Clearly, two cool breezes in the hot sweltering days of Summer!
Thanks!
I know you're with "the Other company"... but, in all fairness, you too - have been equally as helpful - to many of us, as we attempt to not brick our devices in our valiant desires to upgrade and flash anew! Such levels of end-user dedication is not often seen nor experienced in the world of today's "Instant Gratification Generation".
Lol, what do you mean "the Other company?"
Sandy Korda
09-06-2008, 08:45 PM
No offense. I just thought you were with... uhm, er, I mean, like... "Sprint". You know, "The Other Guys".
MstaCDLite
09-06-2008, 09:05 PM
those steps didnt work for me... In addition to the problems that I have been having with the connection, my signal strength most of the time shows 0-2 bars of strength. I'm in a good location that has great service, but the phone hangs around 0 or 1 bars. I did not have any connectivity issues until I first upgraded the Radio to version 3.27. I didnt realize there was a newer one so I went to 3.35. before the Radio upgrade my connections were fine.
Are there any steps that you had to take with this verizon tech that helped? I have done countless resets, removing the battery, reconnect attempts, PST tweaks, etc. and still no luck... and then once in a while it will connect and then stay connected to the data for a few hours until it randomly disconnects again and cant log on.
help has been greatly appreciated...
-Clark
No offense. I just thought you were with... uhm, er, I mean, like... "Sprint". You know, "The Other Guys".
Lol, read my signature...I have an xv6800 ;)
Sandy Korda
09-06-2008, 09:33 PM
...:P
(Assuming the position...) Boot to the Head!
Sorry Dude. Was focusing on the problem and not the message, nor the messenger.
My bad.
MstaCDLite
10-06-2008, 09:44 AM
wondering if maybe a new radio would help this issue?? Im running out of ideas. :(
wondering if maybe a new radio would help this issue?? Im running out of ideas.
What rom are you using?
MstaCDLite
10-06-2008, 10:22 PM
I am using n2c 5067 ROM...
I resolved the issue myself! This is what I did...
Lucky for me I had my old 6700, I went into MyAccount online and activated that one, took the battery out of the 6800, Went back to MyAccount and reactivated the 6800, put the battery in, did *228, took the battery out again, booted it back up, set up a new dial-up networking profile (called it My Connection, used #777, username 7digitnumber@vzw3g.com, password vzw, set it as the default connection) and zing! I’m back in action. My data connection is on, strong and GPS works... What a PITA!
Hope others can use this method if they cant figure it out like me...
And honestly I dont know what made me do those steps, but I was shocked it worked. :)
worthingtonmedic38
14-07-2008, 06:00 PM
Just thought I'd add my current experience in here. I have been using DCD's 3.2.1 with my XV6800. My camera developed an issue (Plus sign in the picture as if a camera pixel was bad or something) so i decided to go back to the stock Verizon ROM before talking to tech support. Flashed back, talked with tech support about the camera, they are shipping me a new one.
After flashing the stock radio i had the typical authentication error, called in and got it taken care of, but my data hasn't worked since flashing stock. I'm getting the error code 11 / PPP error. I updated to 2 different radios and 3 different DCD ROMs which had worked great for me in the past, still no data.
I finally settled with radio 3.42.30 and DCD 3.2.2, still no data and now my wifi is kicking me off as well. I tried installing Verizon's WirelessSync just for kicks but no change.
I checked the espt settings noted above and i also have blanks in all the wrong spots.
I will try the above ideas today or tomorrow and report back.
You guys amaze me and crack me up all at the same time, I glance through the titan forum about every night. Thanks for helping us normal tech challenged folk out!
Just thought I'd add my current experience in here. I have been using DCD's 3.2.1 with my XV6800. My camera developed an issue (Plus sign in the picture as if a camera pixel was bad or something) so i decided to go back to the stock Verizon ROM before talking to tech support. Flashed back, talked with tech support about the camera, they are shipping me a new one.
After flashing the stock radio i had the typical authentication error, called in and got it taken care of, but my data hasn't worked since flashing stock. I'm getting the error code 11 / PPP error. I updated to 2 different radios and 3 different DCD ROMs which had worked great for me in the past, still no data.
I finally settled with radio 3.42.30 and DCD 3.2.2, still no data and now my wifi is kicking me off as well. I tried installing Verizon's WirelessSync just for kicks but no change.
I checked the espt settings noted above and i also have blanks in all the wrong spots.
I will try the above ideas today or tomorrow and report back.
You guys amaze me and crack me up all at the same time, I glance through the titan forum about every night. Thanks for helping us normal tech challenged folk out!
Did you ever flash a sprint rom to obtain a radio? If so, did you accidentally let the customizations run?
worthingtonmedic38
17-07-2008, 05:34 AM
Yes i have flashed a sprint ROM, but was careful not to let the customizations run as instructed, soft reset as soon as the countdown began. As far as i know i did everything right, but who knows... It worked great until i flashed back to the stock verizon rom as instructed in the WIKI for returning the Titan to stock. Anyways, i've been slammed at work and did not have time to troubleshoot my original phone with verizon before the new one came. Activated the new one a couple hours ago and it connected to data first attempt without setup, works great, no error codes. I checked the ESPT info on the new unit and there is as you stated encrypted data in the following fields:
Security
HDR AN AUTH Password
PPP Password
M.IP Default Profile
HA Shared Secret
AAA Shared Secret
As i recall these fields were all blank in the malfunctioning unit, although i was unable to view ESPT settings in the old unit after activating the new unit. Thanks for your interest.
dAg0d
25-08-2008, 05:21 AM
lets say u did let the sprint customizations run...
how would u fix that?
cuz my internet doesnt work and it thinks im connected to sprint. (i have Verizon)
nitro66215
25-08-2008, 03:01 PM
lets say u did let the sprint customizations run...
how would u fix that?
cuz my internet doesnt work and it thinks im connected to sprint. (i have Verizon)
1) Download the Verizon Carrier Cab... install it... and then soft-reset.
2) Check EPST. Follow this and edit the settings...
MDN = HEX ESN #
Edit data settings to vzw dial ##778 and enter your new msl of 000000
MIP Profile
Number of profiles: 6
Active user profile index: 0
MIP_MODE: Mobile IP Prefered
MIP Reg Retries: 2
MIP Reg Retry: 1750 ms
MIP Pre-Reg Timeout: 0
Mobile Node-HA: Enable
Send A Reg: Disable
Dormant Handoff Opt: Enable
MIP Default Profile
Enable Profile: Enable
NAI: mynumber@vzw3g.com (MDN@vzw3g.com)
DUN NAI: (if entry is there enter MDN@vzw3g.com so you can tether without a tethering package or MDN@dun.vzw3g.com if you want paid tethering))
MN HA SPI Set: Enable
MN HA SPI Value: 12C
MN AAA SPI Set: Enable
MN AAA SPI Value: 0 (requires a "2" here for 6800 and 6900)
Reverse Tunneling: Enable
Home Address: 0.0.0.0
HA Shared Secret: (erase whatever entry is here leave blank)
AAA Shared Secret: (erase whatever entry is here leave blank)
Primary HA Address: 255.255.255.255
Secondary HA Address: 255.255.255.255
DMU Pub Key: 10
MN Authenticator: 0
Also, Check that under settings, connections, connections, advanced... under Verizon Wireless... select Edit.... the # should be #777 then a couple "Next" screens... the Username = Phone#@vzw3g.com. Password = vzw. Leave the Domain blank.
SOFT-RESET
dAg0d
26-08-2008, 08:08 AM
thanx alot man that worked but now the internet only works for a little bit then it says wrong password, i change the pass to vzw and the same thing happens over again.
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.