Hi all, please help..my verizon sch i730 always show me error message like below every i try to connect to internet using #777 :
-----------------------------------------------------------------------
Dialed #777
No modem at above number. to check your connection setting and change them if needed, tap setting
-----------------------------------------------------------------------
i'm sure my username and password are correct.. my phone already upgraded to wm5. my data connection already set to "internal data call".
need help please
the others errors message appears :
---------------------------------------------------------------------------
the answering modem has disconnected. to check your connection setting and change them if needed, tap setting
---------------------------------------------------------------------------
Do a soft reset and try again. There is a program in the startup folder (\windows\startup) called CDMACSP that recreates the dialup connections on the device. By default you don't need to make any changes when trying to connect from the i730 to Verizon.
If that doesn't work, make sure you have done a *228 and option 2 to update your PRL list, and make sure you are in a Verizon area, and not in an extended area.
I am assuming you are trying to just connect from the phone and not trying to tether.
If you deleted CDMACSP from the startup folder, hopefully you backed it up someplace and can at least click on it and run it. It removes and recreates the #777 and #7772 dialup connections.
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
I recently was experiencing the "the answering modem has disconnected" problem. However, it would not occur 100% of the time. Instead, I typically would be able to connect just fine a couple of times after a soft reset but then--after 2-4 successful connections--I was unable to connect until I soft reset the i730.
I tried all the other suggestions made in various threads, including asking Verizon to reprovision my i730 and updating my PRL. None of those suggestions worked so I ended up performing a hard reset and slowly have been adding software/hacks to try to determine the culprit. The problem re-occurred when I did the auto-disconnect hack that is described in this thread:
Interestingly, after I did the hack and noticed that the problem re-appeared (just 2 days ago), I tried to open the registry to ensure I did the hack correctly. It's a bit difficult to describe, but my registry seemed quite messed up (entries that should have been there, weren't). I restored from a back-up I had done just before I did the hack and then re-did the hack. Now, things seem to be doing better. I'm going to try it for another couple of days, though, just to be sure.
So, hopatz, my question to you is: Have you done the auto-disconnect hack? If so, you might try undoing the hack or doing a hard reset to see whether that solves the problem.
Let us know whether you are able to resolve the issue.
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
Last edited by iProb8 : 01-14-2007 at 10:31 PM.
Reason: Need to clarify problem
hopatz, just two more questions: 1. By any chance, are you using phoneAlarm 1.58? 2. What software are you using?
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
In recent weeks, getting both of these error conditions in a couple of NYC ZIP Codes. In addition, the data connection tends to time out intermittently (say, after a few mins of "inactivity"). You click on a link, it redials #777.
This behavior is a cousin of our old friend, "Dormant" mode.
Definitely a network/tower issue unrelated to the device (although some PPC designs may be more sensitive than others). Filed two tickets, will follow up.
In recent weeks, getting both of these error conditions in a couple of NYC ZIP Codes. In addition, the data connection tends to time out intermittently (say, after a few mins of "inactivity"). You click on a link, it redials #777.
This behavior is a cousin of our old friend, "Dormant" mode.
Definitely a network/tower issue unrelated to the device (although some PPC designs may be more sensitive than others). Filed two tickets, will follow up.
--BAM
Somehow, I don't think I, being in Phoenix, was affected by the NYC problem.
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
FWIW, this morning I received the dreaded "the answering modem has disconnected" message. I wonder whether it has something to do with the fact that I had my ActiveSync schedule set to manually connect on weekends but automatically connected on weekdays.
I've changed my settings to manually connect all days and will see whether I continue to receive the error message throughout today.
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
iProb8 :
1. no i never do that..
2. no i'm not using phonealarm
after done hardreset i trying again (*228 option 2 also) to connect my phone to #777 but still fail.
is there's any patch for verizon i730?i need to change setting on my M.IP to simple ip but dont know how do that.
hopatz, if you're having problems connecting after performing a hard reset, you should call Verizon's data tech support. They may need to "reprovision" your phone for data. If reprovisioning doesn't work, they'll probably send you a new (refurbished) phone.
As to dormant mode, my understanding is that dormant means your phone is connected to the data network but not actively sending or receiving data. Some of the more technical folks here can correct me if I'm wrong.
Good luck and keep us informed.
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
Reviewed this behavior (in two adjacent NYC ZIPs) with VZW engineering (way beyond Tech Sppt--they call back to follow up on trouble tickets assigned a prefix of "NRB," whatever this means...).
Engineering confirmed the problem is the tower and will dispatch field service to fix it.
What we did was change the device network default to 1X from Hybrid via dial code **492743 (HYBRID), and then soft-reset. In 1X mode, the timeouts and #777 redials disappeared.
Thus, the issue is out-of-spec EvDO gear. Will report when proper connectivity is restored.
--BAM
P.S. The key to getting results on these kinds of elusive problems is eliminating as many variables as possible BEFORE calling the first time. Don't waste time with hard resets and *228s, point 'em to what's really wrong.
Reviewed this behavior (in two adjacent NYC ZIPs) with VZW engineering (way beyond Tech Sppt--they call back to follow up on trouble tickets assigned a prefix of "NRB," whatever this means...).
Engineering confirmed the problem is the tower and will dispatch field service to fix it.
What we did was change the device network default to 1X from Hybrid via dial code **492743 (HYBRID), and then soft-reset. In 1X mode, the timeouts and #777 redials disappeared.
Thus, the issue is out-of-spec EvDO gear. Will report when proper connectivity is restored.
--BAM
P.S. The key to getting results on these kinds of elusive problems is eliminating as many variables as possible BEFORE calling the first time. Don't waste time with hard resets and *228s, point 'em to what's really wrong.
BAM, I'm not sure I understand your p.s.
When I called Verizon data support a couple of weeks ago (the first time), I asked them to reprovision my i730, which they did (I based this request upon something I read in another thread about the "answering modem disconnected" message). As it turned out, reprovisioning the phone did not solve the problem. Consequently, I called Verizon data support again. This time, the tech wanted me to hard reset my phone. I told him I didn't have time right then to do a hard reset and screw around with reinstalling all my software. He told me to do a hard reset on my own and that if the problem recurred, I should call back and they would send me a replacement phone. When I got around to doing the hard reset, I figured I would eliminate variables by adding software/hacks slowly and monitoring what happens. So far, the "answering modem has disconnected" message has recurred only when I performed the auto-disconnect hack (see post #4 above) and when I have push e-mail enabled using ActiveSync. If I change ActiveSync to sync only manually, I don't receive the error message. I next was going to try editing the registry to lengthen the amount of time before the phone automatically disconnects from the network. I also was considering removing phoneAlarm 1.58 because my partner uses the hack and phoneAlarm 1.57 without any problems. Thus, I'm wondering whether pA 1.58 has anything to do with the error message.
Do you think I'm going about my troubleshooting the wrong way?
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
I've been having the same problem. I undid the auto-disconnect hack and put the original registry values back in, but that didn't fix it. It seems like this problem only started occurring when I started using ActiveSync Push. Any ideas?
I've been having the same problem. I undid the auto-disconnect hack and put the original registry values back in, but that didn't fix it. It seems like this problem only started occurring when I started using ActiveSync Push. Any ideas?
What third party software are you using? What, if any, hacks have you done?
I'd like to see whether we can find a common denominator to this problem. I re-did the auto-disconnect hack because I didn't like my connection being on constantly and then I just disabled ActiveSync push. I haven't had the problem occur since then and it's been about 2 weeks since I've been operating this way. I would like to go back to push e-mail, but I want to make sure the connection is terminated.
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
I'm doubtful that this is related to other software, but there is always that possibility. I'm thinking it has more to do with WM5 and ActiveSync Push, and the way it reacts when you go out of range or faulty EVDO equipment in the cell site. I think the problem only started occurring when I started using ActiveSync Push.
Having said that, I have a lot of software & hacks installed. MRailing's hacks, PhoneAlarm 1.58, ewallet, Mortscript, Schedule+, Tasks+, and a few others. I think the only ones that would possibly affect the radio or data connection would be the hacks and PhoneAlarm.
I'm doubtful that this is related to other software, but there is always that possibility. I'm thinking it has more to do with WM5 and ActiveSync Push, and the way it reacts when you go out of range or faulty EVDO equipment in the cell site. I think the problem only started occurring when I started using ActiveSync Push.
Having said that, I have a lot of software & hacks installed. MRailing's hacks, PhoneAlarm 1.58, ewallet, Mortscript, Schedule+, Tasks+, and a few others. I think the only ones that would possibly affect the radio or data connection would be the hacks and PhoneAlarm.
I've been wondering myself whether pA 1.58 could be part of the problem. I never had the problem when I was running pA 1.57. I can't remember why, but I did a hard reset. I then installed pA 1.58. That's when the problem started occuring. If I have some time, I might try reactivating push e-mail and then removing pA to see whether the problem disappears. If you're feeling adventurous and do the same, please let me know the results.
Jay
__________________
-Jay The Fine Print:Nothing in this post (or any of my other posts) is intended to constitute legal advice or the establishment of an attorney-client relationship. For purposes of this forum, I'm just another nerd like you. :-)
You can always turn on logging on your phone and then send the log file to Bruce over at pocketmax.net (in the forums there), and see if he notices anything weird, tell him you are having lockups. Bruce is wonderful to deal with, and if it is his problem with the software, he will fix it.
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
Well, I haven't seen the problem in 2 days. I didn't make any changes on my end, so I'm more inclined to think that Verizon was doing work on their cell sites around my area.
Dialed #777 : No modem at above number
Login
Panel
