Related
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..
Hey guys,
Here is the scoop, my Dream was working perfectly and all of a sudden my phone said no service.
After troubleshooting a bit and no luck I decided to wipe the phone and start fresh in case I installed something that messed it up, still nothing.
I took my sim card out and cleaned the contacts with rubbing alcohol to make sure all was good and still no service. I then decided to use only 2G and my service came back. According to Robbers my account is good because I tried my sim card in an IPhone 3g and I get full reception in 3g no problems.
I cant find any info on this..Can anyone help?
Same here
Same here, fastest way I found to fix it was to reboot the dam thing...
God I hate myself for installing the last "mandatory" upgrade...
Rebooting didnt help... the ONLY way I got service was to force only 2g.. nothing else worked.
Check that you have the proper apn settings. Some ROMs don't have them right/don't have them.
I'm on Robbers latest e911 fix rom... unrooted no cooked rom installed.
Hi Guys,
Wondering if anyone could help? I think I may have turned my DHD into an expensive mp3 player! I don’t seem able to connect to any mobile network Apart from that the DHD functions perfectly (working wifi/gps) - it has been working fine in the past
I can’t make/receive any calls / text message. When I try to connect to a mobile network I receive the following error:
- If I choose the network manually myself (o2 for me) I get "Your sim card does not allow a connection to this network"
- If I try going for the automatic option I get "Unable to connect to this network at this time. Please try again later."
- I'm also getting the notification every 10 minutes to "Set current time" - I don't know if this is related but I assume so since both issues started at the same time!
The problem occurred when I decide to give RCMix a go through ROM Manager. It appeared to flash fine and was running smooth and quick until I noticed a few hours later I had no mobile connection I'd done this a few times before with RC 7 and CoreDroid and hadn’t experienced an issue before.
First thing I tried was to recover to my previous setup before the flash (using ROM Manager) - the phone restored however the mobile network still remained unresponsive! ...this was the same for all my previous backups. I tried clearing cache and dalvik-cache. I even tried reformatting the phone at one point.
I know it's a fault with the phone and not the sim, I'm just not sure what. I've tried my sim card in another DHD and it worked fine. I have also tried different o2 sim, an orange, vodaphone and T-mobile sim card in my phone – all of which give the same problem.
I’ve tried resorting the phone with a few different RUU’s, and even a German one just because it was o2 branded and I’m on contract with them:
- RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed
- RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed
- RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed
- RUU_Ace_O2_DE_1.32.207.1_Radio_12.28a.60.140e_26.03.02.08_M_release_153755_signed
I then re-rooted the phone with the use of Visionary+.
I’ve tried turning the radio off then back on, both by switching airplane mode and by using the hidden option *#*#4636#*#* and I’ve also tried re-flashing the radio and even a different more up-to-date radio:
- Radio_12.28b.60.140e_26.03.02.26_M (original)
- Radio_12.39.60.19_26.06.04.06_M
I’ve checked out the APN and it appears to be correct for o2.
I’ve done simpler things like restarting / powering off, removing the battery, re-seating the sim, re-seating the sdcard and booting without the sdcard!
All in all I’m running low on idea’s Could anyone please help or throw some idea’s at me, it would be very much appreciated!
Thank you.
bobuk said:
Hi Guys,
Wondering if anyone could help? I think I may have turned my DHD into an expensive mp3 player! I don’t seem able to connect to any mobile network Apart from that the DHD functions perfectly (working wifi/gps) - it has been working fine in the past
I can’t make/receive any calls / text message. When I try to connect to a mobile network I receive the following error:
- If I choose the network manually myself (o2 for me) I get "Your sim card does not allow a connection to this network"
- If I try going for the automatic option I get "Unable to connect to this network at this time. Please try again later."
- I'm also getting the notification every 10 minutes to "Set current time" - I don't know if this is related but I assume so since both issues started at the same time!
The problem occurred when I decide to give RCMix a go through ROM Manager. It appeared to flash fine and was running smooth and quick until I noticed a few hours later I had no mobile connection I'd done this a few times before with RC 7 and CoreDroid and hadn’t experienced an issue before.
First thing I tried was to recover to my previous setup before the flash (using ROM Manager) - the phone restored however the mobile network still remained unresponsive! ...this was the same for all my previous backups. I tried clearing cache and dalvik-cache. I even tried reformatting the phone at one point.
I know it's a fault with the phone and not the sim, I'm just not sure what. I've tried my sim card in another DHD and it worked fine. I have also tried different o2 sim, an orange, vodaphone and T-mobile sim card in my phone – all of which give the same problem.
I’ve tried resorting the phone with a few different RUU’s, and even a German one just because it was o2 branded and I’m on contract with them:
- RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed
- RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed
- RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed
- RUU_Ace_O2_DE_1.32.207.1_Radio_12.28a.60.140e_26.03.02.08_M_release_153755_signed
I then re-rooted the phone with the use of Visionary+.
I’ve tried turning the radio off then back on, both by switching airplane mode and by using the hidden option *#*#4636#*#* and I’ve also tried re-flashing the radio and even a different more up-to-date radio:
- Radio_12.28b.60.140e_26.03.02.26_M (original)
- Radio_12.39.60.19_26.06.04.06_M
I’ve checked out the APN and it appears to be correct for o2.
I’ve done simpler things like restarting / powering off, removing the battery, re-seating the sim, re-seating the sdcard and booting without the sdcard!
All in all I’m running low on idea’s Could anyone please help or throw some idea’s at me, it would be very much appreciated!
Thank you.
Click to expand...
Click to collapse
Did you try on your phone pad to type *#06# in order to check your IMEI?Do it and check on your phone's box that they are the same
Sent from my Desire HD using Tapatalk
Double check your SIM card slot to see if its clear of any debris. Other than that, there is a definite fault. Was your handset originally branded?
Sounds like a blacklisted imei.
Sent from my Motorola Startac running Atari 2600 software!
HTC HD2 with error connecting to the network problem
I have the same problem! I bought a phone from ebay "new" and I have not been able to connect to my network AT&T. The phone has android gingerbread 2.3.2 Nand, and I have tried everything in the book to see if I can connect to the network but to no avail. I have been going on forums for the last three days, and if anything, I just want to know what is wrong with the phone. My sim works on other phones fine. There is enough signal in the area (ive always had signal where I live), and tried resetting, taking the battery off, flashing different roms, even went back to Winmo and nothing has worked yet. My IMEI on the phone was different from the one the box, but was the same on the phone as on the inside IMEI.
WHat the heck is going on? Please ideas or help!
Hi Guys,
Thanks for the quick replies...
afilopou said:
Did you try on your phone pad to type *#06# in order to check your IMEI?Do it and check on your phone's box that they are the same
Click to expand...
Click to collapse
pwraggcan said:
Sounds like a blacklisted imei.
Click to expand...
Click to collapse
Yes sorry I forgot to mention this part - I tried *#06# and both numbers matched on screen and under the battery hood. I also had the IMEI checked to see if it was blacklisted and it has not...
andyharney said:
Double check your SIM card slot to see if its clear of any debris. Other than that, there is a definite fault. Was your handset originally branded?
Click to expand...
Click to collapse
Tried clearing the slot, there is no visible signs of blockage... also I bought the handset second hand - I've never seen any branding however when I bought it the previous owner did tell me it was previously locked to vodaphone and he had rooted it so that he could use other sims cards. Which is why I orginally tried a vodaphone sim card too.
Thanks for your suggestions so far guys
Just a quick update, I've been grasping at straws and I've also tried a few more bits below, none of which have worked... I think I may have to leave this one to rest. Just wanted to let others know who may be experiencing the same issues
Matching radio and RIL as mentioned here: http://forum.xda-developers.com/showthread.php?t=1040986
Replacing the mtd0.img as mentioned here: http://forum.xda-developers.com/showthread.php?t=691639
It sounds like a fault. If it was network barred you would still receive a signal, for emergency calls. Can you return the handset to HTC for a warranty repair?
andyharney said:
It sounds like a fault. If it was network barred you would still receive a signal, for emergency calls. Can you return the handset to HTC for a warranty repair?
Click to expand...
Click to collapse
I still get a message on the lock screen saying Emergency Calls only - although admittedly I haven't tried calling the emergency services to check if it gets through.
Not being the original in-store purchaser I don't even know the age of the phone but I'm guessing probably over the 12 month warranty period, sod's law - I'll give them a ring and see what they say
bobuk said:
I still get a message on the lock screen saying Emergency Calls only - although admittedly I haven't tried calling the emergency services to check if it gets through.
Not being the original in-store purchaser I don't even know the age of the phone but I'm guessing probably over the 12 month warranty period, sod's law - I'll give them a ring and see what they say
Click to expand...
Click to collapse
My DHD was from the first batch and is still covered by warranty. How did you check to see if the IMEI was blocked?
I had a similar problem to this one. My mobile data connection gave out after my DHD's temp reached about 38 degrees while playing with it in the sun. A little while later I lost coverage completely, same as you. I tried everything, flashing ruus and re-rooting, re-s-offing, everything. Ten different ROMs, radios, kernels etc.
Eventually I gave up, figuring I had confirmed it was a hardware issue, and popped my sim in my old nokia so I had a usable phone and to get on with my life after wasting so many hours. I left the DHD with the battery removed, and ended up not coming home for a couple of days.
When I got home and decided to start playing around with the DHD again to see if I could get it working properly, I noticed the issues were gone.. I've tried to reproduce this problem out of curiosity, leaving the led light on high for a while, making the phone hot. Nothing. Since then I've flashed everything imaginable, and I've switched back and forth between two radios all week. No problems.
Strange, I'm guessing I have some form of hardware damage, but everything is running smoothly now at 1,5 GHz - no unstability of any kind.
I have done that actually! I took the battery off, and put the phone back in the box just to get on with my life. I left it sitting for a day and a half I guess, and I came back BUT unfortunately, unlike you, the problem is still there. The phone tries to look for signal, but it can't connect to the network. It does find the network and identifies it by name, but does NOT connect to it.
Sounds like a hardware fault Bob - Give it back to Rob!
or try and get HTC to fix if still in warranty?
Thanks! I thought so, too!
Hey did you solve problem?
I have had that emergency calls for 2 day,s i am waiting only. Please help.
If you find that your GPRS data connection connects but you have no GSM signal do the following
*#*#4636#*#* choose radio off and then radio on, be sure to be in a location with a STRONG GSM Signal and your phone should connect. I have had the same issue with my Desire HD and have been surviving with this workaround as nobody else seemed to know
Stiill same :S Selected networkd unavailable error
Try changing sim, or it sounds like blacklisted IMEI.
But my sim works on other phones and other sim cards work on my Huawei?
I was reading through this hoping desperately that somebody had found a solution. I had switched to Cyanogenmod recently but had GPS issues, so I tried flashing a new radio and RIL. Now I can't make any calls/texts, etc. as described here.
Tried several other radios/RILs, tried nandroid restore, tried flashing whole new ROM (LeeDroid). Still the same issue. Tried the *# codes listed here, no luck.
Please let me know if anybody has solved this one. I really don't need a paperweight right now...
I'm in Japan for a couple of weeks for work and signed up for the Japan pack that Sprint offers. I spent almost an entire week working with Sprint support ( ) trying to get data roaming working properly on the phone without much luck (voice and text worked great), but yesterday I lost all connectivity but wifi. Figuring I must have changed something I shouldn't have, I saved everything I could and did a hard reset on the phone.
It still won't connect to any networks. I've re-downloaded PRL and device configs over wifi in the settings but it doesn't even attempt to connect to any wireless networks, or see any for that matter.
I have 2 guesses here but I'd like some kind of confirmation here before I take any action.
1: Maybe my radio firmware is corrupted somehow? I'm not exactly sure how to check it but it just doesn't seem to be doing much of anything. In the SIM status page it says searching for network, but I have no way to know if that's really the case.
2: Since the phone has a Sprint SIM, does it has to be on an actual Sprint network to initialize the networks? (Not Softbank's network here in Japan?) I spent over an hour on Google Voice with them last night trying to get an answer/help but got absolutely nowhere.
The phone is currently all stock but I have no problem unlocking and installing recoveries/software/roms if need be. Any ideas what I can do here or am I just stuck without communication until I get home next week?
Usually the best route is to get a local prepaid sim while traveling but honestly I have no idea what sprint offers for roaming in Japan. Check your plan and see if there is an add on needed.
I'm not alone!
Also THIS IS STILL AN ISSUE!
It worked fine for me last time I came to Japan, about a year ago. This time, I only have voice and text, no data. Right now I'm backing everything up to do a factory reset.
Did you ever find a solution to this?
I'm not sure if you've already done your factory reset, but if you're on Sprint, don't do a reset. The phone can't reactivate itself off of Sprint towers. You have to be in the US when you do the reset. I was stuck with WiFi only for most of my time there because I reset mine.
I never found a solution other than dropping Sprint when I got back to the states. Switched to Verizon and never looked back, though I'm not sure what I'm going to do for my next trip with their ridiculous international rates.
I actually got it working last night.
Factory reset and restore over wifi
Update device config over wifi -> handles activation
Update PRL over wifi 3 times
Now it works
Oh, I'm glad it worked. Is yours on Sprint?
Yes, but I may have spoken too soon. It worked for a few hours and now isn't getting back on data. I think it may be SIM related, since I saw a weird SIM error pop up and rebooted my phone, which led to the data working the first time
They must have redone their activation system since I had my issue in July. At that time there was no way for the phone to reactivate without being on Sprint's system.
As far as the data, that's the same thing I had happen and they were never able to solve the problem. It would work for a little while then stop for no reason. If you find a solution I'd love to hear it though.
I'm wondering if I can flash a different radio or something
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).