05-10-2004, 01:52 PM
|
|
|
Join Date: 09-23-2003
|
| Posts:
27 |
 |
|
Same thing happened to me
I'd had my original 7135 since 06/03. Last week, I had the exact same problem--the handset couldn't find a signal, and would give me the same error message. After hours of dealing with phone and in-store Verizon techs, and my own research here and other places, I ended up having a replacement 7135 sent. My "no service" problem started out intermittent, and escalated into complete meltdown.
Thing is, I didn't WANT a replacement, as the device I had was, in my opinion, extremely stable. Certainly more stable than my XP desktops or laptop. Anyway, after a few burps, the replacement is doing fine.
__________________
PRO
|
|
|
|
|