I have been using an unlocked Moto G 16 gig for quite sometime. Never had an issue with it. When it was received, popped in the SIM and worked right away with AT&T.
Last week the earpiece developed a terrible crackling noise. Motorola sent a replacement which they confirmed as unlocked. However, I cannot get any AT&T service with it. It does pick up the APN settings, but just no signal.
Update: AT&T updated the IMEI on my account, confirmed it registered as a Moto G, but still no signal.
Any suggestions?
Related
I have been unable to access LTE on my 32 GB Nexus 5. I went into a sprint store yesterday where all the S3, S4, and Moto X had LTE and yet I still couldn't connect. I have put a SIM card in my phone and the sprint rep confirmed that my SIM is active, and another sprint rep confirmed that the tower closest to my house definitely hsa 4G LTE active.
https://community.sprint.com/baw/mo...ssion?content=/api/core/v2/discussions/138887
https://community.sprint.com/baw/mo...ssion?content=/api/core/v2/discussions/138984
https://community.sprint.com/baw/mo...ssion?content=/api/core/v2/discussions/139079
There is also a thread on reddit:
http://www.reddit.com/r/Nexus5/comments/1q5drw/sprint_lte_problems_nexus_5_general/
I tried re-flashing the factory image last night just in case last night and that didn't solve the problem.
Is anybody on here having this problem?
touchfan said:
I have been unable to access LTE on my 32 GB Nexus 5. I went into a sprint store yesterday where all the S3, S4, and Moto X had LTE and yet I still couldn't connect. I have put a SIM card in my phone and the sprint rep confirmed that my SIM is active, and another sprint rep confirmed that the tower closest to my house definitely hsa 4G LTE active.
https://community.sprint.com/baw/mo...ssion?content=/api/core/v2/discussions/138887
https://community.sprint.com/baw/mo...ssion?content=/api/core/v2/discussions/138984
https://community.sprint.com/baw/mo...ssion?content=/api/core/v2/discussions/139079
There is also a thread on reddit:
http://www.reddit.com/r/Nexus5/comments/1q5drw/sprint_lte_problems_nexus_5_general/
I tried re-flashing the factory image last night just in case last night and that didn't solve the problem.
Is anybody on here having this problem?
Click to expand...
Click to collapse
Yeah, it seems a number of us are having this problem. We have another thread going here: http://forum.xda-developers.com/showthread.php?t=2515200, albeit still unsolved.
I unlocked my moto g on the tesco network still on 4.3 and giffgaff worked great then i got the OTA too 4.4,
since then i lose network connection randomly i tried deleting all apns and starting fresh in case there was an issue,
but no luck figuring this out anyone else had this problem.
If i downgrade it works perfect unsure whats going on. :crying:
Not cool. Out of interest did you unlock via tesco themselves or code from eBay?
My dad is grabbing a phone from tesco tomorrow but uses giffgaff so I'll be interested to see how this turns out.
Sent from my XT1032 using Tapatalk
I picked up a mint verizon s3 local on a trade for some scrap phones I had. So here is my issue. I put in a sim(at&t) and got the switch to global notification but it never gets signal. Phone info shows -120dbm 99asu. Figured since it was free I would play with it and installed hyperdriver rls 16 still nothing. Took everything back to the first stock ics nothing. Currently have it on jb 4.1.1 nothing. I started to wonder if the radio was trashed so I dialed 911 with no sim in the phone and it popped up 3 bars and made the call.
Am I wrong in thinking this phone will work on US networks with a sim? Anyone ran into this problem possibly can maybe point me into a direction to get it working. The phone is clean and not blacklisted and it reads the different sims I have put in it I just can't get any signal to pull up other than an emergency call. I know there is signal my s4 is on the gsm network sitting right next to it.
Thanks in advance, I have been searching since yesterday for a solution.
****update.....Went ahead and took it to 4.1.2 stock and happened to find an old verizon sim. Phone picks up verizons network without issue. Still nothing when using the at&t sim.
It isn't working for AT&T because you haven't set up the appropriate APNs for that network. Google AT&T APNs. Reboot after making the changes. CHECK FOR TYPOS!
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
It isn't working for AT&T because you haven't set up the appropriate APNs for that network. Google AT&T APNs. Reboot after making the changes. CHECK FOR TYPOS!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I thought I would at minimum show signal even without adding the apn. From everything I have read its talk ready just inserting the sim. Will look at adding apn's this morning.
Final update. Still no joy on getting it to work and I listed it for sale.
There's a thread about getting vzw s3 to work on T-Mobile, I'd imagine you'd need to follow a similar process. And FYI, all phones will call 911, sim, no sim service, no service, they'll call 911. My niece was playing with one of my sisters old, no longer connected phones. All of the sudden police and ambulances showed up. She had dialed 911, they tried to return the call unsuccessfully so they used the phones GPS info and showed up at the house.
Eat Play Google
2 months ago a friend of mine bought himself a bad esn motorola droid ultra for Verizon carrier on ebay and it works for T-mobile and AT&T just fine. His droid ultra was running stock android 4.2.2. Just recently I bought myself a bad esn motorola droid ultra for verizon on craigslist that's running android 4.4.4. I'm with T-mobile service, but I like verizon phones so I bought it thinking that it would work for T-mobile. Unfortunately to my surprise when I put in my T-mobile nano simcard, I notice that for the first 2 seconds it would seem like it's connecting because I can see two white bars then all of a sudden it would vanish. And all I see is a black triangle with dark-gray lines next to the wifi signal indicator, and not only that but I would also see something that reads: RESTRICTED ACCESS CHANGED on the upper top left corner. I tried changing the settings to GSM only and still that doesn't work. I tried using the Phone Info app to tweak the settings and still that doesn't work. So my best guesses are 1) sim tray is bad. 2) it has a bad esn so verizon blocked the phone from being used because an Apple tech person told me that Verizon, T-mobile, and AT&T shares one database where they keep and block all bad esn phones. 3) Motorola disabled the gsm radio on the 4.4.4 android update because Verizon didn't want people on T-mobile service using this particular droid ultra phone on the T-mobile network, so that's why Motorola was so quick to release the 4.4.4 android update for it. Well what other reasons for it not working for T-mobile I don't know. I guess I'm stuck with a giant ipod-touch like android media player. Any suggestions on how to get T-mobile to work on it would be great.
The Sim may be bad. My tmo Sim just went bad.
Sent from my XT1080 using Tapatalk
@work said:
The Sim may be bad. My tmo Sim just went bad.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Just went tried it with an AT&T nano sim-card from my brother's iphone 5, and the droid ultra was able to pick up signal; and make phone calls and send text messages right off the bat. I figure it could be my T-mobile card so I went and bought a regular standard size T-mobile sim-card, and had it trim down into a nano size sim-card; but unfortunately it still wouldn't work. So my guess is that in order for the droid ultra to recognize the T-mobile sim-card it has to be an original nano sim-card. I will go to Tmobile store and buy a nano sim-card and see if it will make any difference. Thanks for your suggestion.
DraghanC said:
2 months ago a friend of mine bought himself a bad esn motorola droid ultra for Verizon carrier on ebay and it works for T-mobile and AT&T just fine. His droid ultra was running stock android 4.2.2. Just recently I bought myself a bad esn motorola droid ultra for verizon on craigslist that's running android 4.4.4. I'm with T-mobile service, but I like verizon phones so I bought it thinking that it would work for T-mobile. Unfortunately to my surprise when I put in my T-mobile nano simcard, I notice that for the first 2 seconds it would seem like it's connecting because I can see two white bars then all of a sudden it would vanish. And all I see is a black triangle with dark-gray lines next to the wifi signal indicator, and not only that but I would also see something that reads: RESTRICTED ACCESS CHANGED on the upper top left corner. I tried changing the settings to GSM only and still that doesn't work. I tried using the Phone Info app to tweak the settings and still that doesn't work. So my best guesses are 1) sim tray is bad. 2) it has a bad esn so verizon blocked the phone from being used because an Apple tech person told me that Verizon, T-mobile, and AT&T shares one database where they keep and block all bad esn phones. 3) Motorola disabled the gsm radio on the 4.4.4 android update because Verizon didn't want people on T-mobile service using this particular droid ultra phone on the T-mobile network, so that's why Motorola was so quick to release the 4.4.4 android update for it. Well what other reasons for it not working for T-mobile I don't know. I guess I'm stuck with a giant ipod-touch like android media player. Any suggestions on how to get T-mobile to work on it would be great.
Click to expand...
Click to collapse
Dude any bad esn from verizon is not going to work with tmobile anymore. T-Mobile and verizon now share block list. At&t doesn't share verizon's bad imei thats why it works with at&t. Before Verizon bad esn phones worked with T-Mobile now it doesn't.
I've got a Verizon HTC M8 running DigitalHigh GPE 5.0.1 12/21 build, stock kernel.
I've had 4g issues with the phone since the first time I ever flashed away from stock. And the whole RUU back to stock and factory reset thing has never worked for me. The phone simply refuses to stay connected to 4G...
The first time I had the issue and I couldn't resolve it I called Verizon. Was sent through to tech support, who "opened a ticket" and told me I would hear from them once it was resolved. Never heard from them, but the issue did go away on it's own and the phone connected to LTE once more on its own. I was running BoneStock ROM at the time (this was back in August 2014).
Fast forward to November and I decide to switch to GPE and I start seeing 4G issues again. My phone would connect to LTE at first boot but once my Sim "activated" it would only connect to 3G from there out. I tried everything to get it back. I did RUU back to stock and factory reset, I flashed new radios, etc...
Finally I activated a new SIM that I had laying around and BAM! LTE service again.
... For a few days. And then back to 3G only.
I used an app called 4G switcher to force my phone to connect to a 4G signal and when I did that it showed that I was roaming... So I would dial *226 and update my roaming list and it would no longer say I'm roaming and would say I'm connected to LTE... For about 10 minutes and then back to 3G only.
I went to the Verizon. Wireless store today and they gave me a new sim and told me to call prepay customer service to see if I can get a warranty replacement. The new SIM instantly connected to LTE and has been connected for almost 6 hours now.
Is there something wrong with my phone that it keeps frying the SIM or could there be an issue with my account on Verizon's end, maybe something telling it to reprogram my SIM to not connect to 4g?
I have used my phone overseas for a month with a European SIM and a service that was only 3G, not sure if that would be relevant at all.
I'm fairly sure your problems aren't on Verizon's side. From reading over the thread, the GPE ROM certainly appears to cause some folks issues regarding LTE service. GPE wasn't designed to run on Verizon. It might be a good idea to stick with something built from a Verizon ROM.
Its a Lollipop thing. Happens on gpe, and Aosp 5.0 ROMs. Just wait till official gets out and they should figure out a fix.