Went to my local call phone store today, got my SIM chip from my old phone put into my new Xiaomi Mi Mix 2.
Make a few calls, and was enjoying my phone when suddenly I started getting "your phone is offline" from google assistant. and a "No service " icon at the top where the cell strength bars are. I also get a "cellular network not available" when I try to make a call.
Any ideas on what happened? I'll go back to the store tomorrow, but this is a bummer.
Thanks.
El Noobo.
UPDATE: This was due to the person entering my MEID number incorrectly at the store. thanks!
Related
I'm noticing 3 strange things:
1) when I go to Settings > About Phone > Phone Identity, my "Phone Number" field shows a different number then mine. They're both in the same area code but it's not mine. I can't edit this.
2) In the Settings > Call > Voicemail Settings, that same wrong phone number shows up. This one I can edit but even then it leads to #3.
3) The voicemail dials the wrong number listed even though I changed the voicemail number. I also receive from time a popup saying that voicemail activation was delayed (or something to that effect). When I do receive voicemails, I receive a text message asking to call a number to retrieve it. Doing so prompts me to enable the service if my phone doesn't have voicemail or something like that. Turned it on and now I can get my voicemail by calling that number.
I should also state that this very same problem happened when I originally got my Evo and I spent about 2-3 hours at the Sprint store talking to one of their tech support on the phone to fix it. But I don't recall having to do anything on my end; it was all the tech supports doing but don't know what.
This has now happened since I rooted and flashed Fresh Evo 3.3. I'm guessing the wiping data/cache removed something that had been fixed?
Hope someone can give me a hand. It'd be much appreciated else I gotta go back and spend 2-3 hours with tech support again. :/
Get your MSL using the MSL tool in the market.
go to the dialer and do a ##786#, do a factory reset(what ever its called in there), its going to ask you for your password, put in the MSL. The phone will do a complete data wipe and reboot. On reboot it will do a complete provision with Sprint.
May work, may not. If not, back to Sprint store.
rjacobs said:
Get your MSL using the MSL tool in the market.
go to the dialer and do a ##786#, do a factory reset(what ever its called in there), its going to ask you for your password, put in the MSL. The phone will do a complete data wipe and reboot. On reboot it will do a complete provision with Sprint.
May work, may not. If not, back to Sprint store.
Click to expand...
Click to collapse
[EDIT: I just figured it out. Hit Menu and then Reset at which point it prompts for the MSL code]
Got the MSL, went to phone and dialed ##786# at which point it says "Retrieving Settings" and brings up the "Reverse Logistics Support" screen. Is this the screen you were referring to? I ask because it did not ask for the MSL password nor did a wipe. Of interest though, I do see an entry for Mobile Number and another one that looks like a cell number but is different then the other; the field is called MSID.
egravel said:
Got the MSL, went to phone and dialed ##786# at which point it says "Retrieving Settings" and brings up the "Reverse Logistics Support" screen. Is this the screen you were referring to? I ask because it did not ask for the MSL password nor did a wipe. Of interest though, I do see an entry for Mobile Number and another one that looks like a cell number but is different then the other; the field is called MSID.
Click to expand...
Click to collapse
Your MSID can be a totally different number than your cell number, mine is. Mine ended up this way when i ported my number off ATT and it has been this way through 4 different phones.
Just the wipe and it went through hands free activation and PRL & Firmware update checks. Unfortunately, the phone identify still shows the wrong number.
So... guess it's of to sprint store?
baknblack said:
Your MSID can be a totally different number than your cell number, mine is. Mine ended up this way when i ported my number off ATT and it has been this way through 4 different phones.
Click to expand...
Click to collapse
Why I wonder if this is not as a result of porting from AT&T as well. Man I really wish I knew what that tech support had done to resolve the issue.
When I update my voicemail settings, or call forwarding, I get a "Unexpected response fron network" error message. I called my provider (Rogers) and said it appears to be correct on their system... However, it doesn't seem so because when people call me, they get forwarded to Google Voice... I already uninstalled Google Voice, and it was taken out already, however, it still forwards to there which is a USA number and I'm in Canada, so people who call me get forwarded to a long distance number and it bothers me and them so much...
Rogers told me to contact HTC but I want to hear your solutions first guys... BTW, I'm using the Virtuous ROM (which is almost entirely stock packages)
Help?
Sent from my HTC Vision using XDA App
did you use the star codes to disable call forwarding?
What are the star code? Already forgot them... heh
Sent from my HTC Vision using XDA App
I was getting the same error and this worked for my desire on orange:-
http://support.t-mobile.co.uk/discussions/index?page=forums&topic=8010386e3edb8701287b5e73bd007174
"Try sending ##21# which is the network code to cancel all forwarding."
Call Forwarding Problem
I have an unlocked AT&T Atrix on Orange UK running Gingerbread. As soon as you go and look at the Call Forwarding options the phone indicates that all calls are Forwarded and the Icon top left turns on, disabling 'Foward All' shows disabled for a few seconds then comes back with the 'Unexpected reponse from network' message, although calls are not actually Forwarded (can still receive calls). Old SIM card, but OK in old V3x phone. I tried with a '3' Network SIM and all works as expected, so definitely an Orange problem with Android/Atrix. I called Orange who sent some SIM updates one of which failed, called them again and they decided to send me a new SIM but this has made no difference at all.
Only way to reset the indicator and message once on, is to enter ##21# which does the job.
Just an annoying Network bug but interested if anyone knows how to get Orange (and I guess T-Mobile) to do anything about this as it seems from other research to affect several different phone makes and models.
Same issue
I'm Having the same issue on Rogers with my Xperia ion....still ahven't sorted it out
Any Resolution to this issue? I have what appears to be an unlocked Samsung Galaxy S7 Active from ATT and attempting to use my CRICKET SIM and I get this message.
I did not receive any kind of visual voicemail on the Xperia Play 4G so I installed the Google Voice app and attempted to configure it to forward my voicemail to the Google Voice service. When selected, it notifies the user in a "Call settings error" dialog box that it "Could not retrieve and save current forwarding number settings" but it offers me the option to "Switch to a new provider anyway?" This, of course, means that it can't read the carrier voicemail number used currently and, thus, can't back it up. It would normally back it up so that it can restore it when you disable GV VM forwarding. Anyway, when I select it anyway, I get another "Call settings error" stating "Forwarding number change unsuccessful." and advising me to "Please contact your carrier if this problem persists."
Anyway, I tried contacting them and they just gave be a new phone which I now know has the same problem.
I tried restoring and reinstalling Google Voice. I Tried it on 2.3.3 and 2.3.4 both with fresh factory restores. Same result. Actually, you can see the service provider change from "My carrier" to Google Voice" the moment you tell it to change it anyway and it once crashed before giving the final error causing it to stay on "Google Voice." What's weider is that it often works even though the phone still thinks "My carrier" is my VM provider.
Anyway, I downloaded the "AT&T Messages" app it gave a similar error too! I'm not sure what it said beacuse I'm not going to reinstall it after something else weird that happened: Google Voice was somehow sending AT&T Messages my incoming text messages and I believe they started billing me for them even though I had it set to receive through the native Messaging app without forwarding (should be free). All I know is that I made a more than a few accidental carrier SMS messages this month when testing GV but that was probably about 15-20 messages and yet AT&T just notified me that I already reached over $20 in charges and that I had used it "excessively."
Now, I switched from an iPhone 4 and did not have voicemail at all for the first month. It could not be set up automatically by phone and required a phone representative to fix it. I'm pretty sure that it was a remanant of my previous iPhone plan's visual voicemail setup. I was using a different qualifying line on the family plan to get the contract setup and, even though they knew what I was doing, they reset that line's voicemail and left mine unuseable. I think there may be some remnant of the previous iPhone config mucking this up on their end and causing my current issues but they insist that they have done everything right.
I do currently have it working even though the phone still thinks that it is set to my carrier. I doubt that GV is integrating it as well as it could when it still thinks that (I probably can't call it from my dial pad, for example). The most immediate assistance would be attempting to do the same thing on AT&T with yours and reporting your results. Any other help, knowledge, or insight would also be appreciated. Thanks!
I am hoping someone on Project Fi can provide insight. I am not able to make or receive calls on my P3XL which has Google Fi service.
What happened was that when I moved to Fi from TMO, I forgot to remove the SIM in the tray. But Fi worked fine with eSIM for 9 months since I moved to Fi Dec. Last week, I had to factory reset the phone because of an unrelated issue and at the fresh boot it found old TMO SIM in there and tried to activate it but gave up because I am not directly subscribed to TMO, although TMO is part of Fi MVNO as well.
I realized my mistake, took out the SIM and activated my eSIM. It showed successful activation for my number associated with the google account. But I can't make or receive calls. When I dial a number, it says "Service is restricted or unavailable" or "Could not complete call". When I dial my number from another phone, it says "Subscriber is not in active service".
Strangely, when I dial my wife's Fi number, it connects and we can talk. The number shown on her caller ID is same temp number (some Texas 817 number) Google Fi assigned to my phone on fresh boot until I enabled wifi, logged into my google account associated with Fi and actually activated Fi, at which point it successfully connected and activated my correct number. But no calls. The data works. SMS does not.
Has anybody seen anything like this? Google Fi support has not been able to help with this so far. The problem was reported on Fri last week and all I have gotten is "we are working on it". I have troubleshooted with them several times, clearing app caches/data, factory reset, safe modes, giving random permissions to fi, phone,google play services and unrestricting data access to all these google apps. But nothing works.
PS: The problem is independent of the OS. I have tried Pie and all recent Q Betas (4,5,6). Its the exact same result.
Does anybody have experience with Google FI support here? My service has been out since Aug 16, and all I get from a supervisor is that "a specialist is working on the case and wait for email from her". I have never had phone service broken for 12 days before ever.
Does anybody with experience with Google Fi support have any hints on how to get someone higher up get more attention to the case? This seems awfully long time for a specialist to figure out why my number is not in active service.
Does your FI number work on wifi?
Does your FI number work through Google Voice?
FI support hit the crapper earlier this year, which is on of the reasons I bailed for Visible. Which has worse support but better service and lower fees.
My recollection is that you just have to call them every day to get it fixed.
parakleet said:
Does your FI number work on wifi?
Does your FI number work through Google Voice?
Click to expand...
Click to collapse
Neither. When I call a number, I get "Service is unavailable or restricted". When I call my number from my wife's, I get "Subscriber not in active service". The Google Fi app keeps insisting that I am activated and service is fully functional.
I am having issues with text messaging, and only text messaging at this time.
- I CANNOT receive text messages when my mobile network is on "AUTOMATIC" or "LTE/CDMA"
- I CAN receive text messages when I am in "CDMA ONLY"
- I CAN seem to send text messages on any network setting.
- Data seems to be working normal.
- I am unsure of incoming and outgoing calls, but seems to be normal.
Things I have done to combat the situation.
- Many "NETWORK RESETS"
- Had Sprint/T-Mobile do "NETWORK RESETS" on their end.
- Replaced SIM card and programmed it as needed with Sprint Tech Support and T-Mobile support.
- Booted and ran several days in "SAFE MODE" to eliminate any app issues.
- I have tried different texting applications
- I have taken my phone to an authorized Samsung dealer, UBreakIFix, and they went through the phone and say that the phone is in perfect condition and everything is working as it should.
I have done everything short of doing a factory reset.
Original purchase date is August of 2019.
Problems like these sometimes can be hard to pin down.
Could be needing a reprovision on your account. Bands not being selected. Blacklisted imei in some shape or form. The device in say like nam programming may be set to read CDMA based instead of gsm based or sim. My s8 had this issue when I went from CDMA to gsm.
Could be incorrect apn settings.
But it seems more like a carrier issue to me as everything else seems to be going ok for you. I would reach out to my carrier and aim for a account and device sim reprovision. Also doesn't Verizon still use that *228 or whatever to do over the air programming and roaming update. Maybe try that too
pip235 said:
I am having issues with text messaging, and only text messaging at this time.
- I CANNOT receive text messages when my mobile network is on "AUTOMATIC" or "LTE/CDMA"
- I CAN receive text messages when I am in "CDMA ONLY"
- I CAN seem to send text messages on any network setting.
- Data seems to be working normal.
- I am unsure of incoming and outgoing calls, but seems to be normal.
Things I have done to combat the situation.
- Many "NETWORK RESETS"
- Had Sprint/T-Mobile do "NETWORK RESETS" on their end.
- Replaced SIM card and programmed it as needed with Sprint Tech Support and T-Mobile support.
- Booted and ran several days in "SAFE MODE" to eliminate any app issues.
- I have tried different texting applications
- I have taken my phone to an authorized Samsung dealer, UBreakIFix, and they went through the phone and say that the phone is in perfect condition and everything is working as it should.
I have done everything short of doing a factory reset.
Original purchase date is August of 2019.
Click to expand...
Click to collapse
Try the LTE/GSM/UMTS setting and see what happens. I have a feeling that more people like you are going to be having problems because of the Sprint/T-Mobile merge. If possible, you should take it to a Sprint/T-Mobile store and see what they can do. They may tell you to do a factory reset. Because Sprint was CDMA/LTE and T-Mobile was GSM/LTE you may need to factory reset to connect to T-Mobile's networks as Sprint's gets shuttered.
TheMadScientist said:
Problems like these sometimes can be hard to pin down.
Could be needing a reprovision on your account. Bands not being selected. Blacklisted imei in some shape or form. The device in say like nam programming may be set to read CDMA based instead of gsm based or sim. My s8 had this issue when I went from CDMA to gsm.
Could be incorrect apn settings.
But it seems more like a carrier issue to me as everything else seems to be going ok for you. I would reach out to my carrier and aim for a account and device sim reprovision. Also doesn't Verizon still use that *228 or whatever to do over the air programming and roaming update. Maybe try that too
Click to expand...
Click to collapse
He's a Sprint/T-Mobile subscriber. Any Verizon info won't help.