Just found out that I can't make any outgoing calls and it looks that is only ICS related. Like most of us, yesterday I installed that first nandroid backup version of ICS, rooted it, flashed glados 2.0 kernel and everything worked great out of the box, 2G/3G data tested, answered few calls, received and sent sms also without problems. Well, today I tried to make my first outgoing call but no success, got "call ended" message immediately after I press phone icon on contact or using a dialer. I flashed new ICS bootloader and radio but that also didn't solve it, then I restored my GB backup and calling worked as before, even with new bootloader/radio. I also can't change those "other call settings" in dialer, it says "network or SIM card error". At last, I wiped everything and flashed today's version of NexusBeam HD ROM and the problem still persists
So, anyone got same problem or solution?
Same here..
Thanks for replying, seems like I'm not the only one with that issue, the only thing that's crossing my mind is that this could be carrier related because we are both on Tele2 in eastern europe... Can anyone else on same carrier confirm that?
I just tried. First attempt failed, like what you described. But all subsequent attempts succeeded. It does seem like there's some sort of bug in ICS.
Really weird, no matter how many times I try, still can't get it working... It's kinda frustrating because I really like ICS as everyone else. However, I'm back to GB and waiting for 4.0.4 or next update which IMO shouldn't be too far because people are getting all kind of issues, seems to me that google released it a bit too early.
Hi, i had the same problem, i needed to upgrade my radio. depending on your phone model pick the compatible one.
download, flash in recovery.
http://forum.xda-developers.com/showthread.php?t=1116884
Thanks for advice, but already tried them all without success. After reading similar cases, I'm 99% sure that's Tele2 problem because everyone who has this issue is on this carrier, calls are working normal with other operator's sim cards in same area. I just emailed their customer support so I'm wondering what their response will be
i had same problem and i tried all radios but to no avail so i just downloaded and flashed the radio that i knew used to work for me. Even though it didn't work i left the phone of for like 4 hrs then turned it on later and it had signal. not sure what changed.
Solved at last, seems that it actually was a carrier issue like I thought. Tele2 responded on my mail after 1 MONTH and all they said was that problem is strictly in my android software... However, few days ago I replaced my sim with their latest, and as soon it got activated the "call issue" was gone... everything works as it should with no bugs so if you have a similar problem with your carrier just try replacing a sim with the newest one.
I like it when people get the problem solved by themselves and return to tell how they did it. Thanks.
Related
I have an HTC Desire. The first one, not HD or Z etc. I rooted using Unrevoked3 and since then tried, with no success, to flash various different ROMs.
The problem I'm having is that right after first loading the ROM, an unending barrage of force close messages flood me (the process com.android.phone has stopped unexpectedly. Please try again), and there's no signal. By struggling my way through all of these FC's, I manage to get to the wireless and network settings and I notice that the Airplane mode switch is being turned on and off repeatedly. The bottom option for the network settings also appears to be going in and out of "greyed out" mode. The only way to stop the FC's is by somehow managing to press the Airplane mode button at just the right time so that it stays on. Once Airplane mode is on, there are no FC's but, also, still there's no signal since it's airplane mode. I can, however, turn on my wifi and internet works perfectly.
So obviously the phones inability to connect to my network is what causes all of these FC's. The question is why?
I have tried several different ROM's, among them a few versions of Cyanogen including the latest one and the latest CM6, Oxygen, DevNull... All had the same issue.
I am wiping my Data, cache and Dalvik Cache before every flash. I tried running Fix Permissions from ROM Manager. I even tried flashing several different Radios. Nothing works!
After restoring my official rooted Sense ROM, everything works perfectly. What the hell is in (or missing from) these custom ROM's that prevents the phone from connecting to my network??
Please, Please help! It's driving me crazy...
Finally got it sorted. The solution seems a bit weird.
It seems that that the cause of the problem was the USIM card that the network provided me when I signed up. It worked perfectly fine with the stock Sense ROM, but once I tried any other ROM, the phone just couldn't connect to the network. After replacing the card with an older version, it suddenly works fine with Cyanogen. It doesn't seem like my card was defective because the same thing happened to a lot of other people with that same USIM model.
Any idea on how is it that a certain SIM card just wouldn't work on custom ROM's, but would only work on the stock one?
ToastMan12 said:
Finally got it sorted. The solution seems a bit weird.
It seems that that the cause of the problem was the USIM card that the network provided me when I signed up. It worked perfectly fine with the stock Sense ROM, but once I tried any other ROM, the phone just couldn't connect to the network. After replacing the card with an older version, it suddenly works fine with Cyanogen. It doesn't seem like my card was defective because the same thing happened to a lot of other people with that same USIM model.
Any idea on how is it that a certain SIM card just wouldn't work on custom ROM's, but would only work on the stock one?
Click to expand...
Click to collapse
Hi ToastMan,
- from which provider is your SIM card? Tmobile, eplus, ...?
- is your Desire SIM-locked (probably not, but how knows ...)?
- from which provider was the working SIM card?
I also have the original Desire and all of the yet installed ROM's (a lot!) worked.
I'm on German Tmobile, last year on Vodafone, never had any problems.
My phone is unlocked. I'm from Israel, so I'm using an israeli provider called Cellcom. Both the problematic and working sim cards are from them. Its just that the one I replaced the bad one with is an older version.
ToastMan12 said:
My phone is unlocked. I'm from Israel, so I'm using an israeli provider called Cellcom. Both the problematic and working sim cards are from them. Its just that the one I replaced the bad one with is an older version.
Click to expand...
Click to collapse
I'm getting old, thought you are from Germany. Maybe I need new glasses Sorry for useless provider questions/info from my first post.
I searched a little bit around in XDA but couldn't find anything which could help. And my knowledge with errors related to SIM cards is very poor.
On ROM side:
You wrote it happend on every custom ROM. Where they all AOSP (=without Sense) ones? I never read that anybody had SIM problems installing different ROM.
Or do you have a CDMA decice and not a GSM model? Than there will be a big problem if you flash a CDMA ROM on a GSM device and vice versa.
They were all AOSP. I never tried Sense based ones. And yes, I paid attention to what ROM version I was downloading. I have a GSM device so I downloaded GSM versions.
so here is the problem I am having with my phone(almost once a day)
I have unlocked it and I have been using for T-mobile
It shows carrier name and also signal strength but when i call any number it would ring but a person on other end would never receive it...same thing happens if someone else calls me they would call me and it would go to my voice mail and i would never receive their call...the only way to find out is when i txt some one it will give me an error saying failure some thing then i would know that the phone is having unusual problem again once i restart the phone it would work just fine then after few hours it will do that all over again..so far this is what I have tried in order to fix it....
odin to stock
tried different roms (froyo, gingerbread)
so here is my take it's not a rom problem..then what is it?
any help would be appreciated and thanks for taking the time to read my problem...
Have u called tmobile and gotten them to text u their settings? I was not getting mms and they sent me a text that i had to install then everything workef
but if it was a setting problem y would it work all this time? like I mentioned earlier that if I restart the phone or tun on/off airplan mode...it solves my problem for few hours...
if you have tried different roms that kind of rules that out which points back to possible network issues, and or hardware issue. how long has the issues been occuring for, and in multiple locations (outside of say a 5 mile radius) or just just one specifci area/location?
edit: maybe you have a different phone you can put your simcard into for a day or two and see if the issue continues?
well I bought this off of ebay and seller didn't mention anything regarding this issue but I think that person was having same issues. It's not a sim card b/c I have tried my sim card in other phones and it works even in iphone 4 originally i was using Iphone 4 I had to turn my sim to mini sim but to make it regular sim I just use the left over piece and it works in other phones w/o a problem. Like u mentioned I have been thinking it's a hardware issue...oh well i m getting rid of this phone pretty quick...thanks to both of u to take the time and answer me...
Hi everybody. Hopefully I am posting this in the right section. I have a Tmobile G2x running CM7 nightly 201. I purchased the phone new (ebay) a couple of months ago. The phone has run relatively smoothly since CM7 installation, until yesterday.
Then, suddenly stopped connecting to the voice, data networks. It will connect via wifi, but would not connect/register for data or voice. It is driving me crazy and is now essentially useless. I have tried to reinstall CM7, I performed system restore to stock rom but the problem persists. It must be an issue with phone since my sim card would work in a different phone, and other sim cards will not work on my G2x.
I have tried to use GetRIl to change baseband. I am now running M6600A-SCAUNTZ-2.0.9720T 1 and I am back to stock rom.
Not sure if there is any way to solve this issue. Should I just resign to buy a new phone? Any solution/setting that I am missing? Can I send back to LG/tmobile a phone which has ClockworkMod Recovery on it? Sorry for the many questions.
You said you went back to stock rom, but did you do a complete restore??
Sent from my LG-P999 using xda premium
italdream said:
Hi everybody. Hopefully I am posting this in the right section. I have a Tmobile G2x running CM7 nightly 201. I purchased the phone new (ebay) a couple of months ago. The phone has run relatively smoothly since CM7 installation, until yesterday.
Then, suddenly stopped connecting to the voice, data networks. It will connect via wifi, but would not connect/register for data or voice. It is driving me crazy and is now essentially useless. I have tried to reinstall CM7, I performed system restore to stock rom but the problem persists. It must be an issue with phone since my sim card would work in a different phone, and other sim cards will not work on my G2x.
I have tried to use GetRIl to change baseband. I am now running M6600A-SCAUNTZ-2.0.9720T 1 and I am back to stock rom.
Not sure if there is any way to solve this issue. Should I just resign to buy a new phone? Any solution/setting that I am missing? Can I send back to LG/tmobile a phone which has ClockworkMod Recovery on it? Sorry for the many questions.
Click to expand...
Click to collapse
Have you tried a full wipe?
Sent from my LG-P999 using xda premium
did you pay your phone bill?
Thanks for the quick reply. I tried restoring to original stock, then erasing all user data. I also tried several times wipe data/factory reset from ClockworkMod Recovery menu. Unfortunately no solution.
Wow, have you tried working as a comedian for a living?
May not be what you want to hear, but it is possible the seller sold you a stolen phone and it has be blocked. You may want to go to T-Moble and have it checked out.
GTWalling said:
May not be what you want to hear, but it is possible the seller sold you a stolen phone and it has be blocked. You may want to go to T-Moble and have it checked out.
Click to expand...
Click to collapse
Thank you. That would at least make sense and I would report it to seller/ebay.
GTWalling said:
May not be what you want to hear, but it is possible the seller sold you a stolen phone and it has be blocked. You may want to go to T-Moble and have it checked out.
Click to expand...
Click to collapse
This, maybe. Also try getting a new SIM card from tmo.
Also, check the IMEI before buying used phones. Even if your phone doesn't happen to be stolen, this is still a good idea.
Thanks. The phone was new from a 100%, long-time Ebay seller. Is there any official website to check for validity of IMEI?
I am going to check with T-mobile but there is also a thread showing other people with similar issue. http://forum.xda-developers.com/showthread.php?p=17660686
Unfortunately, no solution posted. If anybody else has comments/alternative solutions, they will be greatly appreciated.
I received a refurb from t-mobile yesterday and I have been experiencing nothing but problems with the data connection on this new device...
I can also not receive or make calls most of the time, and my old brand new one s didnt do that, now the only way to make or recieve a call is to restart or cycle flight mode...
I will be staring at the phone with a 4g signal indicator full bars and it will go to voicemail after 2 rings... it's supposed to be 3 if I am correct
My friend got a one s like a week before mine and he still has his first one and its working flawlessly
For the record my first one s got shipped back to t-mo for the power button going out.
Has anyone ever heard of this before? I restored the device to factory and I made t-mobile give me a brand new sim card but the problem persists
Having t-mobile send me a new handset tuesday... I never ran the 1.84 RUU on this new device does anyone think this will solve my issue?
I have not messed with this new phone at all yet its completely stock [LOCKED] status
I had similar issues before rooting, custom ROM, and updating the radio. The radio fixed all my issues with data and missing/not being able to make calls. Hopefully, you have an older hboot and can play around (more easily) to find the radio that works best for you. For me, 0.16.31501S16_2_10.22.31501S.10L is great.
teh_pwnrer said:
I received a refurb from t-mobile yesterday and I have been experiencing nothing but problems with the data connection on this new device...
I can also not receive or make calls most of the time, and my old brand new one s didnt do that, now the only way to make or recieve a call is to restart or cycle flight mode...
I will be staring at the phone with a 4g signal indicator full bars and it will go to voicemail after 2 rings... it's supposed to be 3 if I am correct
My friend got a one s like a week before mine and he still has his first one and its working flawlessly
For the record my first one s got shipped back to t-mo for the power button going out.
Has anyone ever heard of this before? I restored the device to factory and I made t-mobile give me a brand new sim card but the problem persists
Having t-mobile send me a new handset tuesday... I never ran the 1.84 RUU on this new device does anyone think this will solve my issue?
I have not messed with this new phone at all yet its completely stock [LOCKED] status
Click to expand...
Click to collapse
Last HTC product I will ever own
I don't know if anyone else has noticed, but after I updated to the latest OTA update (1.25.617.4) I can no longer access call forwarding settings nor call waiting settings. It gives me error saying 'Network Error or sim card error' when trying to view either. I thought it was an issue with my sim cause I just used the one from my HTC 10 so went to AT&T and got a new one only to have same issue. Did a factory reset and same issue. After that I figured it could have possibly been the update, so I used the ROM exe from HTC to get back to 1.21.617.3 and can access those settings again. It was nice to get VoLTE, but I don't want to lose some settings access to get that.
If anybody has had the same issue, have you found a fix other then going back to 1.21.617.3 or staying on 1.25.617.4 and not being able to access call forwarding and call waiting?
Thanks
Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804
holz75 said:
Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804
Click to expand...
Click to collapse
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.
Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I used AT&T.
Click to expand...
Click to collapse
I know, but it's just instructions (from T-Mobile) on how to do it on your HTC 10.
No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.
I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.
mr_salvador said:
No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.
Click to expand...
Click to collapse
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.
Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.
Click to expand...
Click to collapse
Yusuke14 said:
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.
Click to expand...
Click to collapse
I don't know if I mentioned it before but I'm on AT&T, and everything is normal.
I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...
I get the same error message as well. But im on T-mobile. Really doesn't matter to me personally as i don't use settings in there.
But you're not the only one that gets the error.
turbo jjjang said:
I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...
Click to expand...
Click to collapse
Hadn't done anything to phone at the time, was completely stock, nothing done at all as of yet. Only thing i have done now after going back to 1.21 is unlock the bootloader and so far that's all. Going to try taking the OTA to 1.25 again and see if it wasn't just some fluke of nature.
Will update afterwards.
Edit: went back to 1.25, getting same error and can't access call forwarding or call waiting settings.
JWhetstone02 said:
I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.
Click to expand...
Click to collapse
I'm still on the original firmware (no rush to update as of yet) and I get the same situation when accessing those settings.
1.25 RUU is available. I'm on T-Mobile with an Unlocked boot loader and custom kernel however everything works on this end.
I have the 1.25 update and I'm on ATT, and I apparently have the issue as well. No bother, though, since I don't use call forwarding.
And, this is the sim card from my 10.
I am on AT&T and my firmware 1.25.617.4 and everything working fine here
I realize this thread is a a little old but I am having the same issue. I am on AT&T. The only tweaks I have made is to unlock the bootloader and disabled tethering guard. The problem existed on 1.25.617.4 and persists on 1.30.617.2. I thought the problem was a provisioning issue with AT&T. After multiple calls with them and a couple with HTC, I found this thread. Of course I should have stopped here first. I actually need call forwarding and calling AT&T to have them manually provision it every time I need it just won't cut it. Has anyone been able to figure this out?