Related
Hello, like the topic says my phone stopped finding a network. So i can't recive phone calls, sms'es or make calls, etc.
Have you got any idea what may cause it? I just want to be sure if its not my problem before I give it to service.
Normaly I have full connection in the place where I check my phone.
Few days ago I installed new Android 2.1 on my phone and after few days it stopped reciving a signal from network. (no service)
thanks in advance
If Airplane mode is off, and you've set up connections, but it still doesn't work, it may be an update error, or a phone error. Check all settings in Wireless, and if it ain't working after everything is set up, use the warranty.
Hope this helps.
Sent from my E15i using XDA App
It's sim card problem. I plugged it to another phone which worked well and it couldn't find network.
Hi all,
This is my case with the hope of getting any help or lead in order to solve my problem:
After a long research I bought an brand new LG D800 already sim unlocked in the US and brought it to my country (Costa Rica). I made sure the frequencies supported by the D800 are the ones used in my country. In fact 2 years ago I bought another phone that uses same frequencies and had had no problems ever.
As soon as getting in my country I placed the SIM card I'm using in my current phone into the G2 and it recognized the signal and connected to the operators network. I started to make and receive calls almost immediately, and also SMS' without issues. So I started to migrate all my data from the current phone into the G2. I used Titanium Backup for this, so I rooted first the phone using the guide I found here, and basically what I did is installed the apps from Google Play and then restored data using Titanium.
After the second day of use suddenly I found out that I wasn't able to make or receive calls since the phone lost connection to the operators network only allowing emergency calls but the signal bars were full (see scren capture). Sometimes when restarting the phone I get "Phone not allowed MM6" message just after the phone tries to connect to the operators network.
Went to the phone company offices and they tried to help me and made some simple tests, without changing anything inside, such as checking Android's network configurations, checking in their system to verify the IMEI wasn't blocked or reported (the IMEI is clean), also checked the sim configuration and after more than 45 minutes they were not able to find anything wrong in their system or with the phone itself. They also made a final test taking a working sim and put it into the G2 and gatting same emergency calls mode, and took my sim from the G2 and put it in another phone and that phone was able to make and receive calls. So they concluded that the phone has a "built-in" configuration or damage that impedes the phone to connect to the network. They finally suggested to ask the seller to apply the waranty, which is not a viable option since I'm not in the US anymore. This G2 is using the stock ROM (see screen captured).
I've been in close contact with the seller, and he had shown interest in this case but unfortunately hasn't been able to provide much support or help to solve the issue. He reports that he has contacted other buyers of this same phone, also sim unlocked by him, and they all are using their G2s normally. Didn't provide where their locations are tough.
My own conclusions here are that the G2 IMEI is not blocked by the phone company, that there is some kind of fault in the phone that when trying to connect to the network, the network doesn't "like" and rejects connection, althought it worked at the begining, and I'm not able to determine if the fault is software or it's in the hardware of the phone.
So I'm trying to understand what my options are at this moment:
Try to return the phone to the seller, or ask an LG representative in my country to change the unit. Which seems to be very difficult.
Reflash the unit with a stock ROM and reestablish the warranty. But being unsure if this will solve the issue.
Reflash the unit with a new ROM and loose the warranty, and again, being unsure the issue will be solved.
I'm really frustrated and at this moment and have no idea on what to do.
Any ideas or insight will be appreciated.
Thanks.
NOTE: I reinitialized the unit and lost any signal (see screenshots) but received update notifications from Google Play and was able to upload the screenshots into my Dropbox although no signal is shown in the status bar and no WiFi connection is established, only data connection thru APN (I Assume).
Go into status, what's IMEI say?
Sounds like EFS issues. I take it you didn't back it up after setting up on carrier and flashing?
Of so, you have some manual work to do with diag mode and a couple apps via pc.
Hi Steamer;
Under status I see 3 items:
1) Phone Number: shows"Unknown".
2) IMEI: shows the number printed on the box, on a sticker on phone's back.
3) IMEI SV: shows"03".
Where can I learn more about EFS issues? Are there tutorials?
As you say I haven't done any backup thing.
Sent from my LG-D800 using xda app-developers app
Steamer86 said:
Go into status, what's IMEI say?
Sounds like EFS issues. I take it you didn't back it up after setting up on carrier and flashing?
Of so, you have some manual work to do with diag mode and a couple apps via pc.
Click to expand...
Click to collapse
Hi again Steamer:
After reading quite a bit about EFS issues now I understand much better what you meant with your post.
And as you said I didn't back up efs folder, I even didn't flash any ROM yet in the unit. The only thing I did was a 'hard reset' to the unit using the Power + Vol. Down method, after having several 'com.android.phone' errors due to backing up data from Titanium.
The phone went to factory state, I put the sim card and everything went back to normal again, meaning that I was able to make and receive calls. Like 4 hours later the phone went to emergency calls only mode, and from then on I'm not able to take it out of that mode.
So I wonder if the efs folder could corrupt after that factory reset. Is it possible?
Thanks again and any light is greatly appreciated.
It is not in its own partition on this device, but in system. A hard reset shouldn't have caused corruption, but it is not impossible. Your IMEI is intact then, that is good. From what you said about it working partially, your EFS is most likely fine as well. There is a thread here to get files with custom recovery zip file, or you can use adb commands to do it yourself. I don't have guides off hand, but Google is your friend, just specified this phone in searches. Try a new SIM. Sounds more like SIM /carrier issue now as you are out of "activation". That is why emergency is popped and unknown number. The SIM itself may and most likely is bad(or carrier has an issue with your account), in turn it can't communicate with the server causing non activation on network search. Priority to SIM.
franz_cr said:
Hi again Steamer:
After reading quite a bit about EFS issues now I understand much better what you meant with your post.
And as you said I didn't back up efs folder, I even didn't flash any ROM yet in the unit. The only thing I did was a 'hard reset' to the unit using the Power + Vol. Down method, after having several 'com.android.phone' errors due to backing up data from Titanium.
The phone went to factory state, I put the sim card and everything went back to normal again, meaning that I was able to make and receive calls. Like 4 hours later the phone went to emergency calls only mode, and from then on I'm not able to take it out of that mode.
So I wonder if the efs folder could corrupt after that factory reset. Is it possible?
Thanks again and any light is greatly appreciated.
Click to expand...
Click to collapse
Hi i have similar issue with my LG G4 H818P dual sim... after factory reset i often face emergency calls only issue despite full signals... sometimes i able to make and receive calls but most of the time despite my sim registered on network and i get full signals when someone tries to call me he get message as my cell is off.... really annoyed and i flashed latest rom v10e but same issue. Same sim when i use in note 3 then no issue what so ever
Sent from my SM-N9005 using XDA Free mobile app
I had the same issues. Bought in Us using now in India. Go to settings..tethering&networks.. mobile networks... international data roaming and select standard data. Switch off and switch on your phone .
This will happen when you use, internet over gsm. If you disable internet or if your phone loses signal while switching between edge and 3g/4g data, this is tend to happen.
Similar Problem
I have an lg vs980 and I was using it with H2O wireless and later I changed to Simple Mobile. I'm living in Puerto Rico. The phone was working all right and, suddenly, one day it was always displaying 'emergency calls only'.
I did factory reset, then I reflashed stock lollipop and it was like nothing happened, keeps displaying 'emergency calls only'.
Then I found this post http://forum.xda-developers.com/show....php?t=2394689 and applied the patch but didn't seem to resolve the problem.
As a last resort I tried flashing cm 12.1 and before first boot applied the patch from the cited thread but no result, keeps displaying 'emergency calls only'.
Has anyone found a solution to this problem?
Hey, my name is Chris, i'm from Greece and I recently got a Huawei p8 lite ale l21 and i can't make or receive any calls. When I trying call someone i get a "mobile network not available". In dual sim setting i can see my sim working in slot 1 and i have full signal and 4G perfectly working all the time. Also slot 2 is totally useless as when i tried to place my sim there i did not have even signal.
I have searched around the web a little bit but i have not find something really helpful. Any ideas?
It will be helpful to change my ROM to a custom?My current version is C432B170. That was the first thing that i thought but i m not very familiar with that kind of stuff
Edit: I ve install marshmallow 6.0. Nothing changed... Still have 4g, full signal etc but i can't make or receive calls.
Anyone?
Sent from my ALE-L21 using XDA Free mobile app
I was experiencing with similar problems, although the calls were coming through just fine, but after dialing any number, or trying to call from Contacts, the Dialer force closed immediately.
I disabled all installed xposed extension, and my problem was fixed all the sudden after the reboot, and calling works fine since then.
Your problem seems different from mine, maybe you should try swapping the two cards, or try to get them replaced at your carrier.
Also, the ROM has to be dual-sim in order to get the second slot working, and the second slot will work only with 2G and calling.
same problem here...any luck ? :\
http://forum.xda-developers.com/p8lite/help/huawei-p8lite-doesnt-make-receive-calls-t3400468/
CiNi
Hi there
I had the same problem as daviddosa. Except, even I have disabled then uninstalled all exposed module, the symptom still appearing randomly. Now after several reboots and factory reset I could not start calling. Maybe I going to reinstall a stock ROM.
KR
I have been going through a weird issue on Total Wireless. When I use Android 6.0.1 and below, I have no issues with my service at all, everything works as it should. The issue comes into play when I use any Android 7.0 ROM, be it official or custom. Outgoing calls/4G data are fine, but I cannot receive any phone calls or send/receive texts. The only way for me to be able to receive calls and send/receive texts is to dial out once. After this, everything works as it should, that is until I reboot. Then I it goes back to the partial working state until I dial out again.
The issue persists whether I am using CDMA/LTE or Global Network modes. I have tried every single possible combination of starting with a fully working 6.0.1 firmware and upgrading through Smartswitch, with and without a full Wipe performed afterwards, doing a full 7.0 firmware flash. The issue is always present, and I am not sure if TW has issues with Android 7.0 or if there is a problem with my account. Their CS is absolutely useless in helping me with the issue, and our chats always end with if I can make a phone call, then the issue is resolved. They don't understand that the issue is still present, but it only crops up after a reboot of my device.
I have tried 3 different SIM cards and they have deleted and re-added/reprovisioned my device/number to their system but nothing seems to help this issue. APN is the usual TRACFONE.VZWENTP. It's really weird that it happens on two separate devices that I activate with my mobile number.
My only thought as to what it could be is maybe some weird provisioning error with the number coming from Verizon. Total Wireless doesn't have any type of VOLTE capabilities on their network, yet I was able to use a rooted Note 4 device and activate Advanced Calling/HD Voice and I believe Wifi calling as well and use it fine on their service. One oddity I noticed is that when the phone is in the initial 'Searching for Service' state on a fresh boot when I dial out while connected to Wifi, sometimes I will see Mobile Network Type change to IWLAN, whereas it usually says LTE. After dialing everything works correctly.
Any ideas on further troubleshooting steps I can take? If nothing can be done, maybe there is some way I can have a boot up script that makes a ghost phone call to any random number and immediately disconnects so I don't have to remember to dial out whenever I reboot my device?
Thanks
I don't have a solution yet, but you're not alone. I have a stock G935V (running Nougat) with Tracfone service running over Verizon's network. Whenever I start up the phone, the phone will indefinitely remain in a "Searching for Service" status until I initiate one phone call. Then the network instantly switches to "Verizon Wireless" and everything works correctly for as long as the phone remains on.
A long phone call with Tracfone and Verizon yielded no solution: They indicated everything is configured correctly in my account. Various replacement SIM cards didn't change anything either.
This issue happens with both stock Samsung S6 phones and the Samsung S7 phone in my household. All are running Nougat.
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
dbldown7 said:
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
Click to expand...
Click to collapse
Tracfone tried, half-heartedly, to solve the problem by sending me 3 different sim cards. The problem never went away. I just got in the habit of initiating a call to voicemail whenever I restarted my phone.
The problem went away when I upgraded my S7 Edge to Android v8 Oreo.
I have flashed the Nougat "U" firmware on my Verizon S7 Edge. I had VoLTE, hotspot, HD voice when calling someone on Verizon (but the HD symbol doesn't show on my dialer, only on theirs).
Only issue was that. when I introduced the TW SIM, the APN was auto set for Tracfone (and it wasn't working), so I had to manually change it to the TotalWireless one.
Since then I had received the Oreo upgrade and the following security update... and it's still OK.
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).