Hey guys a few days ago I dropped my phone. Nothing broke, the screen didn't crack. Nothing got loose.
After I turned it on there was no more 3G (prior to the drop I always had 3G coverage), My signal dropped to two bars and alot of times it showed as roaming.
I think something inside got messed up, I opened the phone but everything seems fine.
Is there anyway to find out what is wrong? Maybe a diognostics test like cars have that tells me what is failing?
I have done a hard reset, and even reflashed my phone. Nothing seems to work.
If someone can help me out to fix my problem successfully I would give you 40.00 dollars. I really need this phone fixed and cannot afford another one. I use it for work cause its GPS since I travel alot.
Related
I got a used G1 almost a year ago, unlocked it so I could use it with AT&T and it had been working without any trouble until this past Sunday. I was running 1.6 for the longest time and never got around rooting it or installing mods. Suddenly, after I was on the phone for 2 hours, the G1 stopped receiving service. It was normal for the phone to drop service for a moment because of where I live, but after a couple seconds I usually get service again. I didn't.
I swapped out my SIM to an older phone and I was able to get service. So I figure it probably isn't a SIM card problem.
So I put the SIM back into the G1, browsed through the phone to see what was wrong and suddenly found that I had an "update all" button for the market. That's a feature only in 2.2, not in 1.6. I checked online to see if there were any updates to 1.6, but didn't find anything. I had no service, but a feature not in 1.6 on my phone.
After several hours of having no service, I decided to root my phone and install Cyanogen Mod 6. I thought maybe updating the phone might fix the problem. Hours later, I got CM6 up and running and used my brother's SIM to activate my Google account. It just so happened that when I was activating the phone, I had a small window of reception. After that, no service.
Monday I went to the AT&T store to see if they could help and my phone suddenly worked inside the store. I left it there for 15-30 minutes and service didn't drop, so I thought it was fixed. I left and just as I got home, my phone stopped working. So I drove back to the AT&T store to get a new SIM. Sad part is, my phone has service in the store. Again. I just don't get service anywhere else.
I got the new SIM, but I still didn't get service. My brother suggested that the antenna cable might be loose. So yesterday I went to pick up a screwdriver set that had the right size torx bits so I could open up the phone. The cables looked fine, but I pulled them out and plugged them back in. That didn't fix the problem. I still didn't have service.
Late last night, at the CS club at school, a guy with a G1 on T-Mobile put his SIM into my phone to see if it would work. After 5 minutes, my phone was able to connect. So I swapped my SIM back in, but no service. My G1 can see the networks. Right now, I can see AT&T under "Available Networks", but every time I try to connect, it says, "Unable to connect to this network at this time. Please try again later."
I'm using a spare phone right now, but I'd really love to have my G1 working again. Any help or suggestions would be greatly appreciated.
Same Problem
If it makes you feel any better.. 7 months later and I have the same issue. Been scouring the internet and XDA for hours without any resolution. Maybe AT&T is dumping IMEI #'s for devices not in their lineup? Older AT&T Sims seem to work though which is strange. Maybe this bump will get us some kind of response.
Hiya folks,
Bit of weird one here. I can't seem to switch on my WiFi anymore. I turn it on, it tries to enable, but then switches off without any interaction from me. I've done nothing different, software wise, with the phone over the past few months. I did, however, take a 2 hour drive the other day with strong sun coming in the window. I had been using the phone as a SatNav and I'm wondering if maybe it over heated and killed the wifi chip or something. Is this familiar to anyone? I've never heard of it before so any help would be great.
Thanks a million,
T
What rom are you on?
Have you tried a full wipe? maybe try to re-flash if problem still persist or test with a different rom.
I've been working on repairing a htc sensation that got ran over. Had some spare parts so thought i try it out. All that seemed damaged at first glace when i open the phone was the lcd screen and digitalizer. Haven't noticed anythign broken on the board.. I've recently replaced both the lcd screen and digitalizer. The cell phone will not get cell signal and when attempting to turn wifi on, it gives me an error. These both used to work before it was damaged. I was wondering if anyone had a breakdown on the modules inside the phone, like which one was for wifi, and which one was for the cell signal?
So i got the phone to pick up cell signal now. Looks liek when the phone got ran over some of the pins were bent too far away from the backplate. Once i bent it out, it picked up signal just fine.
Wifi on the other hand is still giving me an error. I can't help but think it's hardware since i've flash firmware, radio, hboot, and rom already. Any one got ideas or anything? Where is the wifi located on the hardware?
Thanks for anyone who can help!!!
Hard damage dude...
Im sorry to know that
Sent from my HTC Sensation using Tapatalk
wasn't my sensation =P Mine's perfectly fine. just a friend of mines. Amazingly i've got everything but the wifi to work. These phones are built amazinly. Got ran over and the damage is no where near what i expected it to be.
I searched and did not see anyone else experiencing this issue. I have a Black 32 GB stock rooted. It worked fantastic for about 2 weeks and then all of a sudden I noticed the following:
Day 1: No SMS received. I was on WIFI and had network signal in the notification bar but did not receive SMS that were sent to me.
Day 2: No Cellular Signal. I looked at the APN and it had disappeared. I attempted to add it again and reboot the phone and it wouldn't add. The phone began rebooting on its own and continuing with a bootloop after running for about 10 seconds it would reboot again. It did this throughout the day. I called Google and they had me do some soft and hard resets. After the soft reset the phone would connect right after startup then disconnect after 2 seconds and reboot itself. I hard reset the phone and relocked the bootloader and reinstalled factory recovery and it is still doing it.
Google has given me authorization for an exchange but I was just wondering if anyone had any ideas because I'd rather not be without a phone for 2 weeks.
BTW I am on Straight Talk
I had a similar issue
I had a similar issue. After a month of functioning normally, my Nexus(rooted using CFroot, stock ROM, T-Mobile) lost the ability to get reception. First, it showed network signal, but cell access was not functional. A few hours later, bars dropped to zero, and it seemed like I could only get reception in the strongest signal areas. I would get signal sporadically when driving, but never when I was stationary. The phone never had problems with rebooting though.
After spending a day trying to fix it, factory reset, relock, flashing a factory image, I called Google, and they warranteed the phone.
nebrando said:
I searched and did not see anyone else experiencing this issue. I have a Black 32 GB stock rooted. It worked fantastic for about 2 weeks and then all of a sudden I noticed the following:
Day 1: No SMS received. I was on WIFI and had network signal in the notification bar but did not receive SMS that were sent to me.
Day 2: No Cellular Signal. I looked at the APN and it had disappeared. I attempted to add it again and reboot the phone and it wouldn't add. The phone began rebooting on its own and continuing with a bootloop after running for about 10 seconds it would reboot again. It did this throughout the day. I called Google and they had me do some soft and hard resets. After the soft reset the phone would connect right after startup then disconnect after 2 seconds and reboot itself. I hard reset the phone and relocked the bootloader and reinstalled factory recovery and it is still doing it.
Google has given me authorization for an exchange but I was just wondering if anyone had any ideas because I'd rather not be without a phone for 2 weeks.
BTW I am on Straight Talk
Click to expand...
Click to collapse
flmz said:
I had a similar issue. After a month of functioning normally, my Nexus(rooted using CFroot, stock ROM, T-Mobile) lost the ability to get reception. First, it showed network signal, but cell access was not functional. A few hours later, bars dropped to zero, and it seemed like I could only get reception in the strongest signal areas. I would get signal sporadically when driving, but never when I was stationary. The phone never had problems with rebooting though.
After spending a day trying to fix it, factory reset, relock, flashing a factory image, I called Google, and they warranteed the phone.
Click to expand...
Click to collapse
It just seems so much like a software issue as opposed to hardware that it surprises me they are willing to warranty it... but I guess I'm not the expert.
How long did it take you to get your replacement phone?
nebrando said:
It just seems so much like a software issue as opposed to hardware that it surprises me they are willing to warranty it... but I guess I'm not the expert.
How long did it take you to get your replacement phone?
Click to expand...
Click to collapse
I got a replacement phone pretty quickly. The phone shipped the day after I ordered the replacement, but YMMV.
Why do you think it was a software issue? The problem persisted after I switch back to a factory image. The replacement phone, running the same software does not have the same issue.
flmz said:
I got a replacement phone pretty quickly. The phone shipped the day after I ordered the replacement, but YMMV.
Why do you think it was a software issue? The problem persisted after I switch back to a factory image. The replacement phone, running the same software does not have the same issue.
Click to expand...
Click to collapse
That makes sense that it was a hardware issue. I guess it could be a faulty radio or something. I'm glad to hear you got your device shipped so soon. Did you end up having to pay shipping?
I ran a nexus 5 for about 4 days and went through two of them both having issues holding a signal. Both phones would start with LTE and then drop to 2g go to 3g and then 4g back to no bars and then 2g and 3g. I was stock all the way and I wish the nexus 5 worked better. It could be a software issue as when I took the OTA to 4.4.2 it became worse. All the areas I was in while this happened were areas that were supposed to be strong for 4g and LTE.
That said I I need a phone that is a bit more reliable even though I'm on T-Mobile. I switched to the LG G2. It has a better antennae and doesn't keep bouncing between modes when in various areas.
My already 3 years old nexus 5 is working great, except that I have some troubles with my simcard. My phone isn't detacting it sometimes in the middle of the day, without any proper reason and then I have to restart my phone several times to make it work again. I already tried taking out the simcard and putting it back in but it isnt really helping. I also have the problem that my phone isn't really accessing the internet. Even though the 4G symbol is there I don't have a connection, the only thing that helps at these moments is to turn on and off the airplane mode, that way I can access the internet for a quick time, enough to refresh a web page or send some whatsapp messages. I already tried to tape that area where the simcard is placed to make it more stable, without any success.
Does anyone have an idea what to do? I don't really want to buy a new phone since the n5 is working great for me.
Hey,
had exactly the same with my N5. Not sure if it's related to a securtity update or not. I was not able to get it work again. Probably it's getting worse for you with time. There are some threads around xda dealing with this problem, but - at least for me - there no solution yet.
regards
Same problem here since a few weeks.
If you have updated the radio to the last version, and if you have already tried and got the same issue with another sim card, then it may be a motherboard issue.