Database Develop

troubleshoot - disconnecting from wireless internet

i'm randomly getting disconnected from the internet while chatting or surfing the net. the times i get dropped may vary but i'm normally unable to even stay on even longer than 15 minutes. when i try to reconnect i can sometimes get back on or get this error:
Cannot connect for an unknown reason. To check your connection settings and change them if needed, tap Settings. If the problem continues, reset your mobile device according to your manufacturer’s documentation and try again.
i'm currently running on christian's (wm6.5) clean rom on 3.4 which i flashed on from 3.2 thinking that this may resolve the problem. i contacted my wireless provider about this issue and they basically blew me off saying that unlocked phones won't work with they network. they did try sending some information to my sim after powering my phone but no luck. i've never had this issue before up until 2-3 weeks ago and i've owned the phone for approximately 7 months. my phone has been flashed throughout the 7 months. i've tried fiddling with the network settings trying to fix this, i've deleted the settings and used my connection setup wizard thing to reestablish it, but it continues to happen. i have used my sim on an older phone and i don't get disconnected.
essentially, i have no warranty so i can't go anywhere to fix this issue. i can receive/send text messages and calls no problem and i am getting full reception and this occurs anywhere i'm located. i'm running att in the us.
if anyone has any suggestions as i'm really starting to pull my hair over this issue and don't want to search for a new phone already especially since i've paid so much for it.

bump. if anyone can please help.

Someimes My Nexus One won't send text messages or make phone calls unless I reboot :(

I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue

Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either

I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.

I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile

This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing

next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks

This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).

jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.

hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..

I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.

blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts

I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.

Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.

I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.

Are any of you using task-killers that may somehow be interrupting an important background service?

I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102

Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?

Nexus one not reconnecting to mobile network

My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?

Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.

jacka$$1 said:
Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.
Click to expand...
Click to collapse
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh

Hey!
You dont want to lose your warranty, then use it!
Your phone seems to be faulty...

My phone is experiencing the same problem as of yesterday. Won't connect. Wonder if it's a T-Mobile issue.

laughter95 said:
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh
Click to expand...
Click to collapse
Its only glitchy coz you have stock rom
Cyanogen is really stable and adds alot of features / functionality.
Fair enough you dont want to lose warranty but i remember in the general thread that lots of hardware failures and others can still fix your n1 under warranty even though they unlocked the bootloader.

I too have this problem, hopefully the 2.2 update will fix the problems.

Can you guys confirm if its android or your service provider thats causing this...

laughter95 said:
My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?
Click to expand...
Click to collapse
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!

rensky said:
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!
Click to expand...
Click to collapse
^ it worked! my phone reconnects to the cellular network after what Google/Tmo did for me on the phone!

I haven't tried calling tmobile, but it is NOT something that will be fixed by hopping on cyanogen's rom. I've been rooted on cyanogen's rom for quite some time and this problem still exists on my n1 which is SUPER annoying. I will try calling tmobile to see if they can fix it on their side, but rooting is not the fix here.

I had the same issue. I used anycut and phone info shortcut and changed the wireless default setting to us and it totally fixed the problem. Have not had that issue again.
-------------------------------------
Sent via the XDA Tapatalk App

I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"

I get this too with an at&t phone.
Have asked for a replacement device from HTC (since the reception is crappy to begin with).
I also have audio quality problems when reception is only 1-2 bars.
Will see if the new phone is better.

I had this problem regularly. It hasn't happened once since I upgraded to Froyo, so I think it has been fixed in that release.

sometimes have this too, i fix it by going to the settings > wireless > mobile networks > APN. at first i deleted and retyped my password in the selected APN, now i just click my network in the APN settings, don't change anything and leave. It immediately reconnects after that.
edit: and i have stock froyo & live in belgium.

I got a new, replacement phone from HTC today.
This new phone has a BIG PROBLEM with this issue.
Even if I am only without reception for a couple of seconds (go through the garage, etc.) it will not connect to any network until I reboot.
My old phone would only experience this problem maybe 25-35% of the time.
Very, very annoying!!!

wildfyr said:
I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"
Click to expand...
Click to collapse
I had similar issues and called tmobile support. I was first linked to Google support. They went through the similar process as described by in the first page. (#*#*4636*#*# select USA band etc). While I was on hold, they called t mobile tech support and had them reset network connection and tried to get me onto a different tower etc.
Tmobile support stated that my sim card (had for about 2 years) was the cause of the issue as they can't handle smartphones as well as their new sim cards. They also said the new sim should improve reception and connection stability (Don't see how a new sim could do this but what do I know?). Moreover, they noted my account and told me to go into the nearest store for a new sim card. Went into the nearest tmobile store told them the issue, they pulled up my account and gave me a new sim. Took less then 5 minutes and I have not had the issue with staying connected to the tmobile network.
I will update this after a few days to see if I still have the issue.

I have the same problems that i cannot connect to network here in germany. first i think it was my sim card, but befor i had another provider (E-Plus) where i had the same problems with reconnecting to network. and one day my eplus sim card is broken so i had to buy a new one by t-mobile. i have tried a lot of roms from here (cyanogen/ 5.0.7 /5.0.8T5 Kangorama rodriquezstyle and leofroyo) everyone seems to have the same problems with reconnecting to network. i hope im not alone with my problems and someone can help.

hmm...
Count me as another. I just upgraded to froyo and it went beserk. Had no service for a while. It would only come on after constantly tapping "select network automatically" until it kicked me out of the menu. It started getting better but kept kicking me out of 3g. I set it to stay always on 3g and it seems to be better... still I'm going to call tmobile and see if I can get a new sim as well.
Thanks for the info guys!

help cant connect to network or save proper network or sms settings

a quick history of what I've done so far
Sumsung I897 captivate from ATT unlock and being used on Telus network was working great for about 4 days, then all kinds of problem started cropping up.
Phone came unlocked, I rooted using update.zip from xda, installed rom manager and started removing ATT bloatware, entered SMS and APN info which worked fine.
Yesterday I noticed that where I once got good reception I was now getting nothing and would have to drive down the street before I would get something descent. I thought maybe I'd put it back to stock with rom manager and see if that would help which it did not. It actually made it worse, decided to go all out and use the Odin3 one click downloader just to make sure I was back to stock firmware. This didn't work either but now I can enter the SMS and change the preferred network type but it doesn't save. Preferred network type is grayed out and even though I can change it it never save same as SMS.
Now I can't hold connecting in my living room where my wifes Milestone gets full bars. I tried taking the phone to where I had the best signal and change the preferred network, SMS, and set the network operator but it doesn't save any info, can't find on operator half the time on manual or auto and gave me an error and logged it to #*9900#
I've been at this for 2 days straight and can't figure out how to get it right back to stock, it seems to keep hanging onto the same preferred network and not saving anything I enter.
What can I do to get back to stock, and it has to be something that wipes everything clean, clean, clean, because even the GSM disconnects stay logged under *#*#4636#*#*
***I desperately even tried pulling the batt and SIM card for the night in hopes that would do something.

So, if I'm understand what happened correctly, you bought an unlocked Captivate, rooted it, deleted some bloatware, entered your Telus APN info and everything worked awesome for about four days. Now everything has gone down the hole. Is that right?
If that is the case, then we need to figure out what changed. Using Odin3 would have definitely put you back to stock/unrooted your phone, I don't think you could go back any further than that. If I were you, I would act like I first got the phone. As in, I would do everything you did to it, as if was day one. At one point, everything worked fine. Try to recreate that. You can always look into exchanging it or perhaps Samsung customer support can give you a little more insight to what's going on. Here's the number if you want to try them out.
Samsung customer service - 1.800.726.7864

Thanks, I've gone through the process a few times today from start to finish trying to figure it out ... maybe some of the problems aren't real problems and just limitations that I didn't know where their. I've since flash with odin3+re-partion to the bone stock i897UCJF6 as in not the one click method. It loaded fine but still have the same issue, I can't set preferred network type or get it to keep the number entered into SMSC. I think if I can get passed that I'll be be one the up side of winning. I keep noticing that the log of GSM disconnects never clears or the usage statistics under *#*#4636#*# , I'm thinking its in the same area that other bad data is being held onto instead of being cleared when flash firmware or factory reset.
Is anyone able to change preferred network type? maybe I was never able to change it but I think I should be able too.
I may be wrong in assuming this but I don't think ATT is going to be interested helping me connect one of their handset that I'm trying to use on foreign network, but I could be wrong and is an open option.

*#*#197328640#*#*
debug screen
phone control
network control
band selection
wcdma band
wcdma all
menu->end
used this to lock my phone to WCDMA only so that problem is solved
*** never mind posted to soon it still didn't stick after rebooting
be carefull using the service menu as I have no idea what most of this stuff does

I got the SMS service number issue fix by taking out my sim, swapping in another known working sim from the same network, setting the service number, pressing update and then swapping back. Before every time I tried to update the service number it spit out an "update error" can anybody tell where the SMS config data is stored? on the phone or sim.
The only problem I'm having now is with reception which maybe fixable if I can set the preferred network to WCDMA only. But the button for that option is a light blue colour vs other phones that I can change this setting on. Does the blue mean anything like a locked function or something that set by the firmware as unchangeable?

I need help reactivating my SIM which mysteriously stopped working

Hi I am in need of some help. I will try to give as much detail as possible.
I was talking on the phone 3 days ago and suddenly my call was cut short. The signal icon at the top was greyed out and it had a little x in the bottom. I tried to figure out what happened and at first I thought the cell tower went down because I was unable to connect to 2g, 3g, LTE/4g, nothing.
Next day with my father visiting my house, I tried his phone, put in my SIM, it works, there is signal (nothing greyed out) and I see the name of the phone service at the top left "Personal". His phone with his SIM works as well. Cell towers are working fine. I put my SIM back in my phone, no signal, not able to make phone calls or receive text messages.
At this time WIFI, Whatsapp, the phone itself works. I double checked APN settings from the carriers website, everything matched. I tried rebooting the phone, reseating the chip, selecting towers automatically, manually, and read many many discussions on the web none of which helped. I decided to do a factory reset. Backed up all photos to the computer and proceeded to reset it to factory new. Put in the SIM and same problem. Oh I also in the meantime have spoken with my service provider and they do not see anything wrong on their end.
So now I proceed to restore the phone from a backup on my MI account, all apps restored. Now I try to use Whatsapp and it wants to confirm my account with a text message, that is a problem because I can't receive text messages. I went to my service provider today, they put in a store SIM with a different number and it worked, they assumed I had a faulty SIM and gave me a new SIM with my number, same problem. Now I think it has something to do with XIaomi or MIUI or my MI account. I log into my MI account from my computer and try to add my email under security and it won't let me because it needs verify my account by sending a text message to my cell which of course is not working.
I am thinking of rooting the phone but I imagine I will somehow be blocked there too.
What happened to my phone?
Is my account being protected in some way MIUI, XIaomi or my MI account preventing me from activating my SIM?
Everything I try to do requires a confirmation text.
I want to root the phone but in order to do so I need to request that Xiaomi unlock the bootloader which will require a text message which of course is to be sent to my phone that wont connect to the cell tower.
Was I hacked or spoofed?
How do I go about fixing my situation?

Have you tried changing region and changing back to your country again? That may be possible reason.
For confirmation of code for bootloader unlocking, while applying put your sim card into other phone and that way you'll be able to get code and bootloader unlocked and can flash and try with different rom.
Similarly if your device is out of warranty then you may want to check with the antenna cable inside phone if that is got disconnected or got loosen. I don't if this would have happened or not but this could be issue. Process with precaution if you do so,I won't be responsible for anything.