Sony Ericsson Z520a stuck on 'Searching... for network'
Page 1 of 1
Author
Message
buggsy Posts: 54
Sat Oct 28, 2006 1:52 pm
Z520a has been stuck on searching since last night, figured it'd be changed by this morning, still stuck on searching...(for network)
Ive done the simple stuff, reset, turn off, take sim out, reput sim in, turn on phone, mess with settings, nothing
Did a master reset, all that did was lose all my stuff, didnt help...
Cant call cingular, roomates are gone, and no land line in the apt.
UPDATE: Tried my sim in an older phone, works fine, apparently my z520a just cant grab any signal , any quick fixes? or is it time to get a new one (im still under warranty)
HELP!
Advertisement
peryus88 Posts: 459
Service Provider: at&t
Sat Oct 28, 2006 4:41 pm
Yeah, just use you warranty...save you the hassle. That's the good thing with having phones that are carrier locked, you can usually fall back on the warranty.
sharkbait1943 Posts: 2
Fri Nov 03, 2006 2:54 pm
I started experiencing the same problem at about the same time. I have lived in the same place and had the same phone for over a year (no longer under warranty). Trying to figure out if the phone is the problem (loose wire or some such problem) or if there has been a change to the tower.
As a followup question, could there be something in my complex that is causing interferrence with my signal? As I said, the problem just appeared last week. Strange.
J
elmo01 Posts: 2341
Phone Model: Samsung SPH-M510
Service Provider: Bell Canada
Fri Nov 03, 2006 3:46 pm
if you hop in your car and drive 10 miles does the same thing happen?... the phone to tower range is 3-5 miles...by doing this you are eliminating things in the riddle... if it suddenly starts working its a tower
sharkbait1943 Posts: 2
Sun Nov 05, 2006 1:21 pm
Moved around town and, while I was able to show a connection with the tower via "bars" I was still unable to make a call. The error message "called failed" came up. I am going to go with the assumption that the fault lies with my phone. Loose connection, burned out chip, something of that order.
Am I making a logical assumption here, or should I look at something else?
, any quick fixes? or is it time to get a new one (im still under warranty)
View more 
