Question NON-STOP sim issue on my xt-2093. am i the only one?? - Moto G Play (2021)

from at&t , unlocked.
ever since i got it as a used christmas present, and tried my 2 TMO sims in it,
ive been dealing with "emergency calls only". ive tried every apn tweak i know, and a factory reset, the ONLY way of fixing it (temporarily) is putting the sim back in my prior phone , then back in the moto.
i'm beyond pissed and ready to throw this miserable junk in a dumpster!
is this a software defect? is anyone else plagued with this curse?

i need help, why are you ignoring this?? i need to know if anyone else has the same issue.
do you know what a forum is made for? REPLIES. so get with it!

Related

[Q] Full 4g data working, but not voice

Ok, so i'm new to this whole android thing and came up on a TB. Sorry for the noobness of this...i did a search, but couldn't find anything relating to my problem. hoping someone could give some advice.
I tried to activate it the other day and it took some time to activate(i guess Verizon's network was down), but the 4g LTE was fully functioning. Phone was recognized on my account at verizon and everything checked out.
however, when i tried to make a phone call, i got the message 'welcome to verizon wireless. your phone number is not active or invalid'. one thing i did notice was the roaming triangle above the signal bars. btw, i did try contacting verizon and they didn't know what was going on..they kept blaming the downed network.
i couldn't get it to work so i had to switch back to my whackberry.
Anyone know what the problem is and how to activate it? any advice would be awesome!
thanks for the help in advance!
Might need a new sim card...
Sent from my ThunderBolt using XDA Premium App
i tired two sim cards already...no luck.

[Q] Can verizon detect a custom ROM?

I just got done SBF'ing my phone (DX2) from the Atrix ROM because I didn't know about A-Key's and thought I lost something major. Anyway, I still plan on running a custom ROM but does anyone know if Verizon could detect that by chance when I call to get my phone re-authenticated? I don't want to call them twice in a matter of an hour or so.
AFAIK VZW cannot tell the difference. Furthermore, I don't think they care how many times you *228, as I've done it multiple times over the past week or so, and I know my friends done it a couple of times in an hour when he was first starting out with his DX. VZWs primary concern is that your MEID matches what they have on record, and isn't reported as stolen. They only really care if you have a custom rom on your phone if you take it in for repairs.
Ok, thanks. Just to clarify I'm not doing the *228 activation. It's activated and I can text, browse, etc. but I cannot place calls because my A-Key was wiped somewhere along the line. I have to dial #8899 and actually speak with someone. That's where I'm concerned about whether or not they will be able to detect the ROM and in turn void my warranty.
I don't believe they'll be able to detect the ROM, but have you tried *228? I just don't understand why you would have texting/data but not voice.
Yes I have done *228 twice. The problem is that the A-key (authentication key) was lost during one of the hard resets. I'm not sure why it happens but it does. I'm also not sure how you retain texting/data but lose voice. Here the thread I found that has a little more detail and the solution to the authentication problem:
http://forum.xda-developers.com/showthread.php?t=363967
Reading through that thread it doesn't seem like getting the A-Key would create any complications. Those people were in the same situation as you, and if they wanna know why you had a problem, then you had to hard reset, after installing some wonky programs cuz you're a dev.

sim card issues

Just realized i posted this in the wrong section over here.
I apologize if this has been answered elsewhere, but I havent had time to research.
Upgraded to ICS official on my AT&T Note last night. No issues. Got up this morning, and grabbed the phone. It said "no sim card emergency calls only"
This happened once before since i have had the phone. To rectify this I did a factory reset and that fixed the issue.
Now, I can do a factory reset, and it may come back and work, but within a few minutes i get the no sim card error again.
Any insight on possible fixes?
Thanks in advance.
lurch519 said:
Just realized i posted this in the wrong section over here.
I apologize if this has been answered elsewhere, but I havent had time to research.
Upgraded to ICS official on my AT&T Note last night. No issues. Got up this morning, and grabbed the phone. It said "no sim card emergency calls only"
This happened once before since i have had the phone. To rectify this I did a factory reset and that fixed the issue.
Now, I can do a factory reset, and it may come back and work, but within a few minutes i get the no sim card error again.
Any insight on possible fixes?
Thanks in advance.
Click to expand...
Click to collapse
Either go to ATT or call to see if they will reset your IMEI for your line ...
If they cant do it over the phone maybe you do need a new simm....they are free...I would take in to ATT store if one is in your area...

[Q] Able to send text, but not receive texts.

Hello All,
I have been looking around and seeing if anyone else is experiencing the same issue I have. But I have not had much luck. I have seen similar cases, but for whatever reason, some of the workarounds found that worked for others have not been successful for myself, or are temporary.
For the past three months, I have been experiencing an off and on issue where I am unable to receive texts, but I am able to send out text. And it is something that I would not realize until people actually notify me, or it is awkwardly silent on the "texting front", which makes me second guess myself. Almost every other week or two weeks this has occurred. At the time, I am running Darky's 8.8 [4.1.2] ROM for the i9300. I have tried rebooting, taking out the SIM, re-flashing Darky and re-flashing Stock (full wipe, etc), and replacing my old SIM with a new one. None have been successful thus far. The only success I have found is that inserting my SIM in a different phones allows the text to flow through almost immediately. I would then place the SIM back in the i9300 and any new texts sent I would receive immediately. After a week or two, it randomly just stops receiving text again, and the cycle continues.
I was wondering if whether this may be a bug with the Android OS itself? I have seen a few posts in regards to SMS being handled by Jelly Bean, but I am not 100% sure if my issue would fall in the same boat. Or if it is possibly faulty hardware? Or some kind of network issue. My network is AT&T, but I'm ruling out a network issue since I am able to receive text almost instantaneously on other phones.
Any information, advice, or help would be greatly appreciated.
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
JJEgan said:
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
Click to expand...
Click to collapse
I've verified that the MMS APNs and SMS settings are correctly configured to AT&Ts network. If it were incorrect from the beginning, I would not get text messages (or MMS) at all. But in this case, it is intermittent and only resolved when I get to "unload" the text messages on to another device.
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
b-eock said:
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
Click to expand...
Click to collapse
Ahh! Thank you b-eock! I don't mean this in the wrong way, but I'm glad that I'm not the only who has experienced this. When this occurred to you, were you on some version of 4.1.2? From what I can remember, this issue never came up until I upgraded from 4.1.1 to 4.1.2. Just trying to find some kind of trend here...
I have had to call up AT&T a number of times regarding this issue. And each time they were of no help. Although they were able to confirm that everything on their end of setup correctly, I got the same BS that you got. And they even gave me the whole baloney that I should upgrade so that they can help assist me better and that since it is not their branded phone, it may not be fully compatible.
I really do not want to give up on this. And I definitely want to find a solution. So I am hoping there is a lucky one out there that has tried different ways of getting fixed. Whether that be trying a new ROM, or downgrading from Jelly Bean to ICS, etc.
Came up a few weeks after I upgraded to 4.1.2 but there isn't really a connection between that. It worked before. Its just random crap. And them telling us everything is good on their end, that's complete BS. They don't know what's going on behind their computer screen.
Same exact thing happens to me. It's ROM dependent i'm thinking. Samsung roms from other countries do it the most for me. Has done it on AT&T and AT&T with StraightTalk. Experiencing it on Purelok HD v3.1 right now. I love this rom but im probably going to go AOSP/AOKP as I don't experience it on those kind of roms.
Camera just isn't the same without the Samsung software to me.

[Q] "Not registered on network" - Tried everything

Hello all,
To put my issue simply, I am receiving the "Not registered on network" error on my phone. I have tried many things to resolve it and to help narrow down the possible problems, I will explain my situation and what steps I have taken to try to resolve it. I appreciate you taking the time to read my detailed explanation in advance, as I wish to be as clear and informative as possible.
My phone is an unlocked Australian Galaxy S3 (GT-I9300). I bought it about 6 months ago and about two months ago had some issues with the display come out of the blue. I was able to get this issue resolved through my warranty. When I received the phone back though, I thought it was all working fine but then I noticed I couldn't send SMSs or make calls as my phone wouldn't connect to my phone network (Vodafone). I tried reboots, hard reboots, restoring backups, using a different SIM card (from a different carrier) and I still couldn't get it to work.
During this process of trying to fix it myself, I rooted the phone. So when I realised I couldn't fix it and it could possibly be a hardware issue, I sent it back to be fixed under warranty. Unfortunately my warranty was voided when I rooted the phone, even though it was broken before I rooted it.
So a few days ago I received my phone back again and spent about 6 hours trying to fix it. Here's what I tried...
I tried to flash the latest Australian firmware (XSA) which is the same as the one I initially had when I purchased the phone. I tried factory resets, different firmware flashes, custom ROMs, different modems etc. None of this worked. I thought I had found my solution when I stumbled across ARIZA's patch, but event this did not solve my problem.
The really strange thing is I can occasionally connect to the network and if I try repeatedly, I can sometimes get an SMS to send. I've checked my SIM is clean (I've tried another SIM anyway) and everything seems fine.
My IMEI number is still intact and isn't blacklisted. I've tried restoring backups from when it was working (before I got it "fixed" the first time) and that's not worked. The current status of my phone is:
ROM: Omega v5.0
Version: 4.2.2
Baseband: I9300XELLA
Network: vodafone AU (sometimes shows as Unknown)
Mobile Network State showing as "Disconnected", except in rare moments
IMEI and Serial intact
I've tried all I can think of and all the suggestions I can find on the Internet. I'm hoping someone here will have some suggestions for things I can try. I'd really like to fix this issue as I've been without my phone for months. I'm thinking it could be a hardware issue, but want to make sure I've exhausted all options I can try myself first before trying to get a place to repair it. As my warranty is void, I'm not sure how easy this will be.
Thanks in advance for your time and suggestions,
Jay.
.:Jay:. said:
Hello all,
To put my issue simply, I am receiving the "Not registered on network" error on my phone. I have tried many things to resolve it and to help narrow down the possible problems, I will explain my situation and what steps I have taken to try to resolve it. I appreciate you taking the time to read my detailed explanation in advance, as I wish to be as clear and informative as possible.
My phone is an unlocked Australian Galaxy S3 (GT-I9300). I bought it about 6 months ago and about two months ago had some issues with the display come out of the blue. I was able to get this issue resolved through my warranty. When I received the phone back though, I thought it was all working fine but then I noticed I couldn't send SMSs or make calls as my phone wouldn't connect to my phone network (Vodafone). I tried reboots, hard reboots, restoring backups, using a different SIM card (from a different carrier) and I still couldn't get it to work.
During this process of trying to fix it myself, I rooted the phone. So when I realised I couldn't fix it and it could possibly be a hardware issue, I sent it back to be fixed under warranty. Unfortunately my warranty was voided when I rooted the phone, even though it was broken before I rooted it.
So a few days ago I received my phone back again and spent about 6 hours trying to fix it. Here's what I tried...
I tried to flash the latest Australian firmware (XSA) which is the same as the one I initially had when I purchased the phone. I tried factory resets, different firmware flashes, custom ROMs, different modems etc. None of this worked. I thought I had found my solution when I stumbled across ARIZA's patch, but event this did not solve my problem.
The really strange thing is I can occasionally connect to the network and if I try repeatedly, I can sometimes get an SMS to send. I've checked my SIM is clean (I've tried another SIM anyway) and everything seems fine.
My IMEI number is still intact and isn't blacklisted. I've tried restoring backups from when it was working (before I got it "fixed" the first time) and that's not worked. The current status of my phone is:
ROM: Omega v5.0
Version: 4.2.2
Baseband: I9300XELLA
Network: vodafone AU (sometimes shows as Unknown)
Mobile Network State showing as "Disconnected", except in rare moments
IMEI and Serial intact
I've tried all I can think of and all the suggestions I can find on the Internet. I'm hoping someone here will have some suggestions for things I can try. I'd really like to fix this issue as I've been without my phone for months. I'm thinking it could be a hardware issue, but want to make sure I've exhausted all options I can try myself first before trying to get a place to repair it. As my warranty is void, I'm not sure how easy this will be.
Thanks in advance for your time and suggestions,
Jay.
Click to expand...
Click to collapse
Return to a stock rom and use triangle away to reset the counter, retry with your provider, they may let it slide that you've previously tried.
It would appear that you've already tried everything.
Return to stock and update via OTA, remove root, remember to use triangle away, I personally haven't had to do it but i would imagine that it needs root privileges to complete so thinking about it i would say to use triangle away first.
Hope you get it sorted.
dladz said:
Return to a stock rom and use triangle away to reset the counter, retry with your provider, they may let it slide that you've previously tried.
It would appear that you've already tried everything.
Return to stock and update via OTA, remove root, remember to use triangle away, I personally haven't had to do it but i would imagine that it needs root privileges to complete so thinking about it i would say to use triangle away first.
Hope you get it sorted.
Click to expand...
Click to collapse
Hey,
Thanks for the quick response.
I doubt they would let it slide as I had a pretty long back and forth with them trying to get them to fix the phone or at least send it back to me without charging me for the shipping costs and that didn't end in my favour. I'm sure they'd remember that they already rejected it due to it being modified and would just blame the rooting for the issues.
I'm thinking I might just reset it all to stock, reset the counter and at least ask. If not, I'll try to find a repair shop who will take a look. Thanks for the suggestion. I'm still open to any other ideas people might have which I can try from my end.
Thanks,
Jay.
Starting point would be correct firmware modem and CSC for your location and network .
Flash your original rom .
Check
http://forum.xda-developers.com/showthread.php?t=1978840
jje
JJEgan said:
Starting point would be correct firmware modem and CSC for your location and network .
Flash your original rom .
Check
http://forum.xda-developers.com/showthread.php?t=1978840
jje
Click to expand...
Click to collapse
Hey,
Thanks for the suggestion. I believe I have tried this by downloading the latest firmware from SamMobile and flashing that through Odin, but I haven't tried it through Keis, so I guess I'll give that a go.
I'll let you know how it goes.
Thanks,
Jay.
Me too. I've an i9305 (S3 LTE) and i've tried every tutorials on internet and so far nothing: always the same issue "not registered on network". In case you solve the issue please let me know. I'll do the same. Txs
I've tried to connect my phone using Keis and it just seems to say "Connecting..." forever. I've tried running the connection troubleshooter and that just seemed to re-install the drivers but not actually fix the issue. I still can't get Keis to even connect to my phone.
Any ideas on why this would be? Or other suggestions I can try for my initial problem?
Thanks,
Jay.
As an update to this, it seems I've tried everything I can on my end to fix it to no avail. I believe it must be a hardware issue and have dropped it into a phone repair centre. I'm hoping they will be able to find the problem and fix it.
I'll let you know how it goes.
Another update to this, I received a response from the repair centre. They said:
"...we took it all apart and checked all connections and serviced it.
Once we put it back together we tested it with Vodafone and Optus sim cards. Both sims had service and were able to connect to the internet as well."
After I asked for more details on what they did to try and help me determine what the problem was, they said:
"The phone looked 100% fine inside, no signs of water or any other damage. Sometimes electronic devices can be a bit temperamental, maybe the fact that we undone and cleaned all connections it's booted it back to life."
So I'm going to pick it up tomorrow, but it sounds like it's all sorted now. So not it's not 100% clear what the issue was, but to anyone having this same problem who has tried everything like I did, it is likely a hardware issue. Your best bet is probably to try a repair shop (assuming your warranty won't cover the problem).
Thanks to those who offered suggestions and good luck to those with the same problem.
Do please tell us if it worked because i'm tempted to do the same as you did before selling it on ebay as faulty for parts. PLEASE ANSWER US BACK AFTER TESTING IT an entire day. THANK YOU A LOT!
Does it work properly now? Thanks - Please reply.
Not sure if it is exactly the same problem but I remember getting that msg when i was on Telstra and I'd installed a new ROM - I went to the Telstra site and got them to send an activation msg that reset my provider info. It didn't seem to matter for phone calls but I wasn't getting any connection to do with data until I 'ran' the msg they sent.
Hi I had this issue with my gs2..what I did was flash the right modem and restore efs thats how I solved my problem..hope this helps..
Sent from my GT-I9100 using xda premium
ichigo200 said:
Hi I had this issue with my gs2..what I did was flash the right modem and restore efs thats how I solved my problem..hope this helps..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Txs for help but I don't have the backups of my efs folder... so I think it is useless therefore i am going to sell it on ebay as faulty for parts. Unfortunately! I love my i9305!
You should probably do some more searching on site - there are a number of things to do, including getting a service centre to fix it. Be cheaper than a new phone. Is it an i9300 or ann i9305?
pmmfilipe said:
Txs for help but I don't have the backups of my efs folder... so I think it is useless therefore i am going to sell it on ebay as faulty for parts. Unfortunately! I love my i9305!
Click to expand...
Click to collapse
Ask a service centre for a fix price first .
jje
Homervy She
Journyman16 said:
You should probably do some more searching on site - there are a number of things to do, including getting a service centre to fix it. Be cheaper than a new phone. Is it an i9300 or ann i9305?
Click to expand...
Click to collapse
It's a i9305 and I've tried everything, every tutorials on internet without success so far. I am tired of the situation and also very disappointed therefore I think i will sell it as faulty. As it regards to a repair center, near my area it's very difficult to find someone who can fix it.
For me it seems my connection is still intermittent when using my Vodafone SIM on my S3 (and the same for another Vodafone SIM I tried on this phone) whereas both SIMs work fine on other phones.
I then tried a Telstra SIM on my S3 and it worked fine. So it seems I have a weird problem with my phone where the combination of the S3 and Vodafone doesn't work, but other phones or other SIMs do work.
I think I'm just going to try changing carrier (I've been meaning to anyway) since it seems their SIMs work in my phone.
Really not sure what is causing this issue, but I'm at the point where I just want it fixed and I don't really care how. Hope you find out how to solve your issue.
How is your phone right now? Im also having the same problem. It always say 'not registered to network' everytime i make a call. This happens whenever i turn on the flight mode, then turning it off.. i have a strong signal and i can use the internet provided by my network but i cant make a call or text.. people cant also reach my number. I sent this already to samsung service ctr and they changed the board but its still there whenever i access the flight mode..
caloyski072885 said:
How is your phone right now? Im also having the same problem. It always say 'not registered to network' everytime i make a call. This happens whenever i turn on the flight mode, then turning it off.. i have a strong signal and i can use the internet provided by my network but i cant make a call or text.. people cant also reach my number. I sent this already to samsung service ctr and they changed the board but its still there whenever i access the flight mode..
Click to expand...
Click to collapse
Hi...the same, no solution so far. I am actually selling it on ebay for parts. I simply gave up.

Categories

Resources