I'm curious to know if anyone with a non t-mobile g1 experienced the same.
My phone was working fine this morning until it stop being able to register on the network with the above error. The only thing I did with it this morning was to put on a screen protector. I doubt it's related
A reboot in recovery mode and a wipe fixed the network registration issue so I guess some data were corrupted.
Hi.
I have the same problem now. Have tried to hardreset but still No service..
Can you help me??
avastdh said:
Hi.
I have the same problem now. Have tried to hardreset but still No service..
Can you help me??
Click to expand...
Click to collapse
Just get a new sim card
I have the same problem now - but it is extremely frustrating and I have tried, since I first wrote what is below to downgrade - but cupcake will not let me.
I have an unlocked - but also unrooted G1. I use it in Europe and in the US. While in Europe I got the message to upgrade and without thinking I did. Then while in Europe I could no longer use the phone as a phone. The update went fine and I had ‘cupcake’ but any SIM I put in (T-mobile, BASE etc) there was no signal and when I went to do it manually I got the message “your SIM does not allow a connection to this network”
So I did a hard reset, but then I could not get pas the start screen since I had no data connection (but I did seem to have phone connection again.
In a layover in Atlanta I tried again - I was able to log in and set up and all was great and good. I should note that I have an old data plan and use an alternative APN to access data. This worked fine in Atlanata where there is 3g connection.
Back home no win Florida… no phone service - same as in Brussels. same message. Worth noting - there is no T-mobile 3G service where I live.
After thinking about this for a while I am wondering if somehow I did not get the correct or full radio update…
if this is true - do you have any idea how to remedy the situation or how I would know if this is the problem?
I appreciate any help.
I have the same problem, any news about this?
I had this issue randomly about a week ago. Reboots didn't work, and I really didn't want to go through a wipe/re-flash. I called T-Mobile, they had me reboot [after I told them I had already done it] --- they ended up deleting me from the network and reboot my phone again, which apparently re-registered me on their network.
This is on T-Mobile US (SW Ohio to be specific)
Does anyone has any news about that? I was told that this might be a radio issue, so I tried to downgrade my celphone to version 62.33.20.0H_1.22.12.29, (using fw 1.0 too), it worked for some time then suddenly it gave me the same error that my sim card it's does not allow to this network, so I forced, again, to my network and the same message appear, I tried this sim in another celphone and worked, I tried another sim on my G1 and it didn't worked, this celphone was working when I lived in the US, but here in Brazil it's not working just like there.. my guess is that the Radio in other countries has any bug, does anyone here was able to fix that? any further advice?
thanks.
weird, i have this issue tonight on one of my unlocked g1's that would normally be working on ATT.
I'll update this post if/when I find a cure.
ohgood said:
weird, i have this issue tonight on one of my unlocked g1's that would normally be working on ATT.
I'll update this post if/when I find a cure.
Click to expand...
Click to collapse
I've been having the same issue of and on for a couple of months now with a G1 on Dutch T-mobile with dutch T-mobile SIM card, which is odd. Running CM mods so maybe the fact that i'm runnig non stock fw causes this?
I get this problem from time to time. Almost never around town where coverage is good, but when I'm on the road in a lot of places where coverage from any provider is poor this happens, especially if it keeps having to switch back and forth between roaming and not roaming. I even get this on T-Mobile and they are my provider. Usually a reboot fixes it, but not always. I've never had it last more than an hour though.
Try reflashing the radio on your phone. Sometimes this helps solve odd connection issues.
beav_35 said:
Try reflashing the radio on your phone. Sometimes this helps solve odd connection issues.
Click to expand...
Click to collapse
according to my tries, this isn't related at all. i'd like to check in on this thread and see a known fix instead of maybes.
Had the same problem
I had this problem about a month ago, apparently simcards can go bad after a while; I had the same simcard for 5 years and it became unreadable. I went to a t-mobile dealer, bought a new simcard for $20, and I was finally able to get my connection back. It's a bit of an expensive route, but at least I didn't have to replace the entire phone.
xxvtcxx said:
I had this problem about a month ago, apparently simcards can go bad after a while; I had the same simcard for 5 years and it became unreadable. I went to a t-mobile dealer, bought a new simcard for $20, and I was finally able to get my connection back. It's a bit of an expensive route, but at least I didn't have to replace the entire phone.
Click to expand...
Click to collapse
my att sim is 4+ years old, but works fine in all but one phone in question, with the above error. also, I have a brand new tmo sim that throws the same error, only on that one phone- which leads me to believe its not a sim CARD problem at all.
all my phones are unlocked, in case of weird problems with any gsm carrier.
Looking at your sig, is this one of the phones with gnav? Because some of the earlier techniques of installing gnav have resulted in a "no service" signal. If it is one of the phones with gnav, try pushing the old build.prop files back into the phone.
xxvtcxx said:
Looking at your sig, is this one of the phones with gnav? Because some of the earlier techniques of installing gnav have resulted in a "no service" signal. If it is one of the phones with gnav, try pushing the old build.prop files back into the phone.
Click to expand...
Click to collapse
gave it a shot, used the normal build.trout... and same results. surely someone at tmobile is familiar with this problem ?
Same issue.
I am running cyanogenMod-4.2.12.2 with radio v. 2.22.19.26I on a t-mobile mytouch. I will lose service and the phone will not automatically reconnect to the network. When I manually select my network (wind mobile) it sometimes connects fine and sometimes I get a "your sim card does not allow a
connection to this network" error and must reset. I found this thread code.google.com/p/android/issues/detail?id=2845 where dozens of people running all different hardware (G1-hero) and all different software (stock cupcake, cyanogen, etc) all experiencing same problem. It seems this problem is happening regardless of the network (T-mobile, vodafone, orange & wind mobile). The problem seems to be happening through all different variables. Changing sims does not seem to fix it. Anyone have any ideas, this is very frustrating.
I've seen this issue as well, with the new Canadian provider Wind Mobile.
The issue seems to coincide with new towers being added onto the network. There are minor service disruptions that result in the network being temporarily screwed up. Going into and out of airplane mode seems to fix it every time.
Also note: These minor service disruptions do NOT ONLY affect my phone, but others (different brands) as well.
They've gotten better at adding towers without blowing up the whole network. It started out happening a few times every day. In the last week it happened only once.
Funny observation: When this happens, the DATA SERVICE recovers automatically, even though the signal gauge remains in X-no service mode. This part is probably android and/or dream related.
It is related with network
I've started to have the same issue tonight. I've rebooted several times and changed the SIM card with another from another operator but nothing helped.
Then i remembered that since I bring this phone from Belgium to Turkey, the regulations in Turkey requires the phone to be registered with its IMEI number to the telecomunications supreme board.
Altough i had initiated the registration process months ago, i thought that there may have been a problem with the registration, so i checked the boards web page.
It turned out that my IMEI is not registered and this most probably is the reason for the not allowed connection.
Tomorrow i will try to reach the board officials and i hope it solves the issue.
do you know what happened? i having the same issue right now and cant seem to find a way to solve it..
Hi everyone,
So I had been using the NexusHD Gingerbread NAND ROM for quite some time. About a month ago, my phone would only work if the call was on speaker phone. This was annoying, but I could deal with it. Today, I started having issues where the phone wouldn't connect to the network, and kept saying No Service. I switched over to Typhoon CyanogenMod 3.8.8, and I am still having the same problem with No Service.
I see that there is a hardware fix for the antenna, but I don't want to open the phone if that is not the issue. Where should I start in troubleshooting this to make sure that I don't go in circles? Thanks in advance!
Greg
Just an update in case any searches this thread later. I found out that my SIM card had gone bad. I was getting no connection at all and it was saying preferred network not available. Took it to TMobile store and they just swapped the SIM. Maybe that was more basic than most info on here, but I was having a hard time finding possible solutions other than the antenna fix.
Hey everyone! As the title states, this is a thread for T-mobile users. Lately with T-Mo upgrading their towers to 4G I've been coming into a few issues. The gist of it is that I randomly can't make or receive calls on my Nexus 4, and after some research online I discovered that I'm not the only one with this problem (This is especially true with Lollipop users). I tried the 4G hack with multiple radios, after resetting my APN settings I can make and get calls for about 2 minutes, and after that my problem comes back as if I never did anything at all. I've noticed that I can get it to work after resetting the APN to default, but I can't be expected to do that every 5 minutes throughout the day, its simply unacceptable. What's worse is that I recently got into a contract with T-Mo after being prepaid for the last year and a half.
So my question to all the T-Mo users here is what ROM are you using? Which radios do you use (if you've had to)? Are you using 5.x.x or 4.x.x? Have you had encountered this problem at all, and if so how did you remedy it?
Update: I fixing my problems by flashing a 5.1.x ROM. Although I nearly bricked the phone because the gapps provided weren't written properly which caused the setup wizard to crash.
My v20 drops all calls between 2 and 4 minutes in, and usually around the 3 minute mark. The call drops, signal goes to zero, and a moment later I get a toast message saying "Loading SIM card contacts..." and then I can immediately dial back in.
WiFi calling is disabled, though the setting being on or off doesn't seem to make a difference. I've cleaned the SIM card and added tape to the back to ensure good connectivity - no change. I also went to T-Mobile and they replaced my SIM on the spot but it immediately happened again in the store and in front of the clerk when we tried a call. They've suggested a warranty exchange.
One interesting thing I've found though is that disabling VoLTE calling fixes it entirely - it no longer drops calls, but of course there's no HD voice and I can't use band 12 and they're already cutting back on HSPA coverage.
Haven't found anything else useful via Google or XDA. Even with VoLTE enabled there are no data drops, VOIP calling via hangouts works fine. Anyone have any ideas short of a full exchange? Not rooted and while the LG backup app is pretty good, I really don't want to go through the day-long process of restoring everything if I can avoid it.
Hey there! I had the same issue, exchanged the phone for a new one, and STILL have the same isssue! Did you ever find another fix? This is so annoying and I cant believe a bigger deal isn't being made of it.
Something wrong with ur
operator
Sent from my LG-H990 using Tapatalk
Been owning V20 for about 5 weeks now. The first 3 weeks were pleasant until I started seeing dropped calls. Disabling VoLTE did not help. Changing sim card wouldn't help either.
I'm having similar issues H915 Freedom Mobile.
Was roaming on AT&T in the US when I first did the update. And everything was fine till I was home and on Freedom.
When Wi-Fi calling is enabled. It makes no difference if mobile preferred or VoWIFI preferred is selected. It enables either way after reboot or turning Wi-Fi adapter off and on again.
Incomming calls frequently don't come through regardless of whether vo wifi is on or off. Texts same problem. And persists sometimes on cellular and sometimes on VoWifi.
Get SIM errors, signal drop constantly. And have tried everything I can think of to rectify the issues with zero success.
Anyone with Freedom having similar issues? Or any suggestions I might not have thought of that may be the the cause?
- Chris
I'm on T-Mobile network and had an issue two weeks ago where the phone randomly disconnected from the mobile network and stopped recognizing the SIM. T-Mobile store changed the SIM but it made no change so they offered to replace it but after a hard reset it magically worked.
Today I got the same issue and now the phone doesn't connect to the network (or WIFI for that matter). Before I do another hard reset I thought I'd post here to see if anyone else has had the same issue and if there is a suggested fix. I'm pretty stumped on this one.
I'm not rooted but the phone is unlocked through T-Mobile and I received the OnePlus unlock code but haven't done anything with it. Currently on the 10.0.27 build.
whiteblazer01 said:
I'm on T-Mobile network and had an issue two weeks ago where the phone randomly disconnected from the mobile network and stopped recognizing the SIM. T-Mobile store changed the SIM but it made no change so they offered to replace it but after a hard reset it magically worked.
Today I got the same issue and now the phone doesn't connect to the network (or WIFI for that matter). Before I do another hard reset I thought I'd post here to see if anyone else has had the same issue and if there is a suggested fix. I'm pretty stumped on this one.
I'm not rooted but the phone is unlocked through T-Mobile and I received the OnePlus unlock code but haven't done anything with it. Currently on the 10.0.27 build.
Click to expand...
Click to collapse
Were you on 10.025 build when it first started? If it's happening with multiple phones on multiple software versions,it makes me wonder if you need to file a ticket with T-Mobile on your line. If the Wi-Fi issue is happening only on the newer firmware, it could be the Wi-Fi was a coincidence and that there is something wrong with your network settings on T-Mobile'a side.
10.0.27 could have a Wi-Fi bug, as I'm hearing a few reports to this happening to a few people. But the mobile data side suggests something happening outside of your phone.
I know it's kind of a long shot, but it's what would make sense overall if this is happening on your replacement phone as well.
I don't recall if I was on 10.025 when it first happened, though I want to say I wasn't as I don't believe I have done any updates since it happened. I don't know why the WIFI is also happening, but bluetooth still works just fine (I didn't mention that in the beginning). When I try to select the "SIM & Network" menu in Settings it seems to freeze. If I file a ticket with T-Mobile I believe they would simply want to replace my phone entirely (that's what they were working on the last time I brought this issue to their attention). Just a point of clarification, I'm still using the original phone and having the issue a second time, when a full hard reset (with erasing personal data) seemed to resolve the problem, at least temporarily.
It sucks because I could just reset the phone again and probably fix it but it's a pain to continually restore all the settings, apps, and settings within each app. I could also replace the phone but then I will be getting a locked phone and will have to go through the unlock process again (which I could do, it wasn't all that bad).