Related
Hi!
Rooted with cmahendra's offline Lelus method (and to anyone who's done that, my hat is off to you).
**SHORT VERSION**
Sim goes into the L9. I get bars that show network availability, however I am not able to connect/make/receive phone calls.
**DETAILED VERSION**
Starts like this: I have my CM rooted Aria that works a-ok as far as the network. Phone message memory getting full all the time and incoming texts bounce back, with no way of knowing who sent them. Can't have that, so I buy a stock L9.
Sim works. I want to have Wi-Fi calling, which is the *only* reason I bought the L9. Wi-fi calling is not working: call up T-Mo and they say I need to give a 911 address and all will be well. Ok, done.
Sim works. But no Wi-Fi calling still. Call up T-Mo and they say "Ohhh! you need a "3G-B" (I don't think that stands for gigabyte) sim card" Ohhh and what's your phone model etc etc. I tell them "it's a no-brand phone I got overseas," they don't need to know the model: they didn't with the CM Aria. They're clicking settings on their screen other side of the phone while we're talking: I can feel it.
Sim *stops* working. Need a working phone, so let L9 aside and get a stock T-mo S2. Same issue, cell network not connecting.
Let me show THEM! Ha! I'll unlock it. Unlocked the S2.
Sim still doesn't work.
Put the Sim back in the rooted/unlocked Aria? Network works.
What settings do they have in their stock phones that disallow network connectivity, because in the CyanogenMod Aria I have the phone fully works, GPS, tether, etc etc. In their stock-from-T-Mobile phones, network = nada.
Thank you for reading.
imadiamond said:
Hi!
Rooted with cmahendra's offline Lelus method (and to anyone who's done that, my hat is off to you).
**SHORT VERSION**
Sim goes into the L9. I get bars that show network availability, however I am not able to connect/make/receive phone calls.
**DETAILED VERSION**
Starts like this: I have my CM rooted Aria that works a-ok as far as the network. Phone message memory getting full all the time and incoming texts bounce back, with no way of knowing who sent them. Can't have that, so I buy a stock L9.
Sim works. I want to have Wi-Fi calling, which is the *only* reason I bought the L9. Wi-fi calling is not working: call up T-Mo and they say I need to give a 911 address and all will be well. Ok, done.
Sim works. But no Wi-Fi calling still. Call up T-Mo and they say "Ohhh! you need a "3G-B" (I don't think that stands for gigabyte) sim card" Ohhh and what's your phone model etc etc. I tell them "it's a no-brand phone I got overseas," they don't need to know the model: they didn't with the CM Aria. They're clicking settings on their screen other side of the phone while we're talking: I can feel it.
Sim *stops* working. Need a working phone, so let L9 aside and get a stock T-mo S2. Same issue, cell network not connecting.
Let me show THEM! Ha! I'll unlock it. Unlocked the S2.
Sim still doesn't work.
Put the Sim back in the rooted/unlocked Aria? Network works.
What settings do they have in their stock phones that disallow network connectivity, because in the CyanogenMod Aria I have the phone fully works, GPS, tether, etc etc. In their stock-from-T-Mobile phones, network = nada.
Thank you for reading.
Sim goes into the L9. I get bars that show network availability, however I am not able to connect/make/recieve phone calls.
Click to expand...
Click to collapse
What the heck are you asking? I don't see any understandable questions in your message. I see you blowing off steam.
It does look like T-Mobile cooked your sim. You may need a new one.
Call them again and ask for "Customer Retention" through the automated system. Those people are more knowledgeable. A new sim should be free if they killed it.
Also, a data plan is not required for wifi-calling.
T-Mobile will give you a SIM regardless. They are always free.
I'm not sure as I am unrooted, but most carriers block network access via files in the EFS folder. This folder is VERY delicate. Anything improperly changed here can render a phone useless. If the SIM works in another device, it's not the SIM. Have you tried a different SIM in your phone?
Also, if you're blocked from network access, when you make a call, you should be prompted with, "We're sorry, but this device has been blocked from network access." If you do not get that prompt, then there is something wrong with the phone itself, be it software or hardware.
Looks like the L9 isn't registering in their system. Where did you buy the phone, blacklisted perhaps?
As for fried your sim, why does it still work in the Aria.
As for 3G-B, you probably need a newer sim, others call it a 4G sim... They should send you one free or pick one up free at a local tmo..
Thanks so far folks...
clockcycle said:
Looks like the L9 isn't registering in their system. Where did you buy the phone, blacklisted perhaps?
As for fried your sim, why does it still work in the Aria.
As for 3G-B, you probably need a newer sim, others call it a 4G sim... They should send you one free or pick one up free at a local tmo..
Click to expand...
Click to collapse
You hit the nail on the head exactly clockcycle, it's not registering. Something *in* the phone is not letting it connect, because my sim works successfully in any and every other unlocked phone I have, blackberrys, GMS world phones, the rooted Aria, but in the two "newer-released phones-- the L9 and the S2-- it doesn't work.
Phones are legit. Craigslist and brand new. Worked perfectly until calling T-Mobile for "support". The sim is fine and the goal is to keep it and not get a new one. It works.
My strong guess is that if I put a different rom that is *not* stock, the phone will work fine. It worked fine in the beginning, until I called them to address the wi-fi calling issue and they started poking around in my account, asking questions and clicking on things. I didn't want to address the wifi-calling issue too much because we could go off on a tangent.
You're right kevev, it didn't look like there was a 100% clear question. A lot of story though, to make sure there aren't 50 posts of did you do this and id you do that. A full story gives everyone the most info they need to understand the situation instead of "yo! my phone is not connecting!" which we see sometimes .
So the more clear question is:
"I am experiencing carrier settings *in* my L9 that are blocking me from connecting fully to the network on a perfectly fine sim card, how can I get around these settings and what/where are they."
I think tribalartgod understands what I'm getting at most completely. The inside-the-phone-settings. When the sim is in the phone I have bars, but when going to make a call the screen message is "emegency only". Can't try different sims in the L9 because of the need to cut the sim down. Also the L9 is not unlocked, just rooted. My guess is a de-bloatwared rom is the fix. Looking for answers from people more knowledgeable than me which is most likely all of you. Thanks again!
Craigslist, new, boxed, doesn't gurranty they aren't blacklisted.
BUT, the Aria uses a miniSim, the L9 uses a microSim. Did you cut your Sim yourself? It might be misaligned, cut wrong.
It's less than $2 to get it unlocked..
It sounds like its IMEI blocked dude. This can happen with various insurance or installment plan scams, even to brand new devices. There are options to still use the phone, but you are hosed on T-mobile. I have a blacklisted L9 because the previous owner quit paying his EIP, but it's unlocked so I used it on an AT&T MVNO connected to an AT&T MicroCell (I wanted WiFi calling too, but that won't happen with a blacklisted IMEI). Until you've gone to T-Mobile's chat support and ask the if the IMEI is clean, writing long posts in this thread is futile, and it is pretty clear everybody in this thread THINKS they know what they are talking about, but nobody has simply asked T-Mobile about the status of the IMEI, which takes two seconds.
OK, so I was with T-Mobile forever, and I bought this phone from them at launch. I decided to switch over to MetroPCS by T-Mobile because it's cheaper, so I paid off my phone then unlocked it (Even though I didn't need too, the Metro SIM worked in it before I unlocked it).
It worked fine for two weeks, and I had WiFi calling and everything, and then the RJ5 (I believe?) update came out, and when my phone booted up it said new sim detected, and WiFi calling was gone. My APN settings were set to MetroPCS', so I set it back to the T-Mobile one since it's essentially the same network, but the WiFi calling option is *completely* gone; it's not there, trust me. I call MetroPCS support and they said they can't enable it for devices that weren't bought from them, and I tried to argue like sure you can, send it up to a higher level support team, but I could hardly understand her and gave up.
I went into a MetroPCS store and they had a spare T-Mobile SIM, popped it in, boom WiFi calling was back.
Come OneUI Pie update one, I opt in and update, and voila, WiFi calling is back!
I just downloaded the second update last night, and now it's gone again. This **** is driving me crazy, if anyone can help me figure out a way to fix this I will love you forever.
Wow, that was a gripping good yarn! I think there's a good chance that if you switch to the unlocked G965U1 firmware, it might work. I have an unlocked Verizon S9+ running on TMO, and once I flashed it to U1, wifi calling and volte worked automatically. I'm not positive how it will be with Metro but it is worth looking into. When you flash the collect unlocked firmware, when the phone boots up it will detect your sim and then reboot and configure all the settings for you.
P.S. I don't suppose there's Metro firmware out there?
I don't think there's Metro firmware, because my updates still come from T-Mobile. T-Mobile owns Metro. So what you're saying is flash the firmware via Odin and my phone would be like truly unlocked and I would get updates from Samsung rather than T-Mobile? I don't want to go through all this if it isn't a a certain fix, but sadly there's no way to tell that.
YrrchSebor said:
Wow, that was a gripping good yarn! I think there's a good chance that if you switch to the unlocked G965U1 firmware, it might work. I have an unlocked Verizon S9+ running on TMO, and once I flashed it to U1, wifi calling and volte worked automatically. I'm not positive how it will be with Metro but it is worth looking into. When you flash the collect unlocked firmware, when the phone boots up it will detect your sim and then reboot and configure all the settings for you.
P.S. I don't suppose there's Metro firmware out there?
Click to expand...
Click to collapse
I don't think there's Metro firmware, because my updates still come from T-Mobile. T-Mobile owns Metro. So what you're saying is flash the firmware via Odin and my phone would be like truly unlocked and I would get updates from Samsung rather than T-Mobile? I don't want to go through all this if it isn't a a certain fix, but sadly there's no way to tell that.
For some carriers, the Wifi calling requires the phone to have carrier firmware. Verizon is one. I bought my 9+ from Samsung unlocked, and it didn't have wifi calling on Verizon until I reflashed the phone (using Patched ODIN) to a Verizon firmware and Wifi calling works... as does the Verizon bloat, but most of that can be disabled with Package Disabler pro or similar app.
creedicd said:
For some carriers, the Wifi calling requires the phone to have carrier firmware. Verizon is one. I bought my 9+ from Samsung unlocked, and it didn't have wifi calling on Verizon until I reflashed the phone (using Patched ODIN) to a Verizon firmware and Wifi calling works... as does the Verizon bloat, but most of that can be disabled with Package Disabler pro or similar app.
Click to expand...
Click to collapse
I don't think MetroPCS has it's own firmware for the s9+. Plus, they're owned by T-Mobile now. The plan I'm on is called MetroPCS by T-Mobile lol. This is driving me nuts.
C-4Nati said:
I don't think MetroPCS has it's own firmware for the s9+. Plus, they're owned by T-Mobile now. The plan I'm on is called MetroPCS by T-Mobile lol. This is driving me nuts.
Click to expand...
Click to collapse
Out of curiosity I read around a little bit and it seems to be really hit and miss, which definitely seems to match up with your experience. I did find this post on Reddit from someone saying they got Wi-Fi calling to work with a Metro Sim: https://www.reddit.com/r/tmobile/co...g_volte_not_working_with_metropcs_sim/cymnvhf
Have you come across that, tried any of that?
YrrchSebor said:
Out of curiosity I read around a little bit and it seems to be really hit and miss, which definitely seems to match up with your experience. I did find this post on Reddit from someone saying they got Wi-Fi calling to work with a Metro Sim: https://www.reddit.com/r/tmobile/co...g_volte_not_working_with_metropcs_sim/cymnvhf
Have you come across that, tried any of that?
Click to expand...
Click to collapse
I have not, thanks for the link, I shall try that. Funnily enough, there was a hotfix pushed out last night and WiFi calling not working was on that list. I now have the WiFi calling icon in the notification bar, and it shows like it's on, but it doesn't actually work, and me pressing it does nothing. The setting itself still isn't in connections or anywhere in the settings. This is so dumb, lol.
New to this, but I'll try to explain the best I can.
I've talked to tech support from my old carrier, my new carrier, and Samsung for about 15 hours total. I'm getting absolutely no where.
I purchased a Samsung Galaxy A20 from Spectrum mobile 3 months ago. I ended my service with them and switched to Red Pocket mobile when they had their black friday / cyber monday sim kit deal.
When I activated and ported my number over to Red Pocket I thought there was an issue with the number port.
But going back and forth with customer service they couldn't figure out what was wrong, as my account was activated and they confirmed that they now owned my phone number.
Eventually I realized my device was still locked with Spectrum. They provided me with an unlock code which did not work. They suggested using the unfreeze code which worked, my device said accepted/unlocked.
Phone works, can make calls and send text messages. However,I cannot access data.
My network operator still says Spectrum, and my Access Point name says charter (Spectrum's APN).
I cannot select the Add button, or the Reset to Default button in Access Point Names.
I took this to mean that my device was still locked since the unlock code did not work.
I thought the unfreeze code was specifically for if you attempt too many unlock codes and it locks you out of making more attempts.
That was my understanding, that the purpose of the unfreeze code is to enable you to make more attempts with the unlock code.
Again, I'm not really sure.
But regardless, Spectrum insists that despite it saying that my device is still locked according to their information, that the only way for it to say unlocked on their end is if i actually connect to my new provider, but that they have done everything on their end and that my device is unlocked and I should be able to connect to my new provider.
FUNNY right... in their records it says my device is still locked, but that that's not really accurate, and that it should be unlocked.
However, I have Red Pocket's SIM in my phone. And I can place and receive calls/texts. Spectrum and Red Pocket both use CDMA, so that makes sense to me. But since I am routing through Spectrum still, and I am unable to Add Red Pocket's Access Point Name in my phone, I cannot connect to Data / LTE.
From what I've explained here, do you all feel like my device is truly unlocked?
What is the best way for me to bypass this? How do I get my phone to switch from Spectrum's Access Point Name to Red Pocket's Access Point Name so that I can access Data/LTE ??
Thank you for taking the time to read my plight, and I appreciate any assistance anyone can give me with this.
I am not sure if attempting to root my phone or messing around with those kinds of settings will fix anything. I am not familiar with how to do that, but I will try anything at this point.
I have the A20 under MetroPCS still locked to their network. I can add APN's to it. So not sure why you are having this problem.
Medfordite said:
I have the A20 under MetroPCS still locked to their network. I can add APN's to it. So not sure why you are having this problem.
Click to expand...
Click to collapse
My thoughts exactly. Very strange why I am not able to add APNs.
I talked to a Samsung representative who suggested that it is probably either a software issue or the firmware installed by Spectrum.
When I told the Samsung representative that they assured me that my phone is unlocked (although I don't believe they even know what they're talking about since it is listed as locked in their system), he even went as far as to say that my device may be SIM unlocked, but they may have installed some sort of firmware on their phone that locks the Access Point Name to their server forcing the user to stay with them. Thus the phone will be able to take a new SIM, but it won't do the user any good since the firmware installed on the phone will not allow the user to connect to any other provider's Access Point.
I asked the Samsung representative if it was even legal for them to do that? He said it wouldn't surprise him as corporate giants such as Charter try to monopolize markets. He then went on to tell me that Charter took over as the internet provider in his area about a year ago and no longer has any other internet service providers in his area to choose from.
But again, I don't know if this is actually the case. But does anyone have any thoughts about what is going on or any suggestions as to what other things I can try to do to get connected to my new provider?
A quick update in case anyone in the future is wondering about my issue.
So after talking with another Spectrum customer service representative I have discovered that although my device was SIM unlocked over 2 weeks ago, my device is still carrier locked. They put an initial request for a carrier unlock over 2 weeks ago. Then after calling technical support a few days after that they had put in another request for the carrier unlock. A couple of days ago the representative I talked to went through all of the previous activity logs with my phone and discovered that the carrier unlock kept getting stuck on the end process of unlocking. He opened up another case for me (this will be the fifth ticket created for my account), but I expressed my concerns and doubts with him that it will accomplish anything.
I explained to him that if the issue can not be resolved on their end that I am pretty much out of luck. Since I have discovered on several forums that the Samsung A20 US version cannot be rooted, so there is no way to unlock the bootloader and install Samsung factory firmware to bypass the carrier locked APN on my own. I explained to him that if there was a way for me to do it I wouldn't even be calling, and I would have fixed the issue myself. However, since I am pretty much out of ideas to get my phone to work with my new carrier on my own and Spectrum can't seem to figure out how to carrier unlock my device even though they are LEGALLY REQUIRED to do so, that I am pretty much just about to give up and sell this device as a carrier locked phone on Swappa. He said yeah that's probably what I would do too at this point..
I said LOL, yeah but the problem there is I spent over $200 on this phone that I was only able to use for 2 months, and if I go that route I will likely only be able to get $50 for it.
He said yeah I can understand that that's frustrating, but I really don't see any other options you really have.
They also refuse to provide me with any sort of compensation even though clearly the mistake is on their end.
Bottom line.
NEVER BUY A PHONE FROM CHARTER / SPECTRUM.
Considering their business practices I would never buy phone service / internet service / any service they offer in the future, and would highly advise everyone else from ever purchasing anything from them in the future.
So far it appears that only tmobile networks allow this phone, since at&t does not support VoLTE with this phone (must set to 3g in order to receive texts/calls). I love this phone, but tmobiles cell towers don't offer a good signal in my area (using straight talk w/ tmobile card). So this got me wondering, which wireless carriers can this actually use now days? What do you personally use with this phone, and how is the service? Verizon definetly won't work either, so it looks like I am out of options... Any replies to this would be GREATLY appreciated! Thanks!
You sure? Here's the AT&T white list, more may have been added since...
I am positive. And yes, I have seen my phone on the list. no phone calls or text messaging when on LTE (and at&t). I looked into changing the IMEI so that I could use a random generated one that matches an s20 or some other phone that is more compatible, then gave up on it. At this point Im looking to sell my s10 lite so I can buy a oneplus 8T/Pro, just so I get better compatibility. Supposedly AT&T is also dropping support for international versions of cell phones, which this is. I went through 3 different at&t sim cards and all have the same result. I just wish there was a way to change my IMEI (or somehow spoof a different phone some other way)
On The Go Repairs said:
I am positive. And yes, I have seen my phone on the list. no phone calls or text messaging when on LTE (and at&t). I looked into changing the IMEI so that I could use a random generated one that matches an s20 or some other phone that is more compatible, then gave up on it. At this point Im looking to sell my s10 lite so I can buy a oneplus 8T/Pro, just so I get better compatibility. Supposedly AT&T is also dropping support for international versions of cell phones, which this is. I went through 3 different at&t sim cards and all have the same result. I just wish there was a way to change my IMEI (or somehow spoof a different phone some other way)
Click to expand...
Click to collapse
Is VoLTE enabled etc in hidden phone settings?
Did you have AT&T reset it on their end?
Talk to AT&T advanced tech support.
If white listed it should work!
I have straight talk which gives three options: at&t, TMobile, or Verizon (so I can't call att directly). I went into the hidden menu settings and VoLTE was turned off and greyed out. I even opened a file and added a few lines (might have been build.prop or something like that, don't remember) and all that did was switch it on in the settings (but still greyed out).
When I called straight talk tech support and asked them to provision VoLTE, all they would say is that the sim card is provisioned, and that's all they can do. Phone and text used to work if I set it on 3g (instead of lte), but this was less than optimal. I also read a reddit post today from someone four hours away that said they killed off the 3g now, so I'm not going to try using another at&t card until I get a different phone that is compatible. I know this phone is capable of VoLTE but at&t sucks, and they want to force a bunch of people to upgrade to newer phones for whatever reason.
I've even had this phone work with a Verizon sim card swapped from a different phone, but after a few days it gets shut off. So it's not a question of compatibility more than it is at&t just being jerks.
OnTheGoRepairs said:
I have straight talk which gives three options: at&t, TMobile, or Verizon (so I can't call att directly). I went into the hidden menu settings and VoLTE was turned off and greyed out. I even opened a file and added a few lines (might have been build.prop or something like that, don't remember) and all that did was switch it on in the settings (but still greyed out).
When I called straight talk tech support and asked them to provision VoLTE, all they would say is that the sim card is provisioned, and that's all they can do. Phone and text used to work if I set it on 3g (instead of lte), but this was less than optimal. I also read a reddit post today from someone four hours away that said they killed off the 3g now, so I'm not going to try using another at&t card until I get a different phone that is compatible. I know this phone is capable of VoLTE but at&t sucks, and they want to force a bunch of people to upgrade to newer phones for whatever reason.
I've even had this phone work with a Verizon sim card swapped from a different phone, but after a few days it gets shut off. So it's not a question of compatibility more than it is at&t just being jerks.
Click to expand...
Click to collapse
Straight talk maybe the issue. I don't know for sure. Maybe it's the sim card.
Both my N10+'s N975U, N975U1 made the jump seamlessly, no changes were needed on my side.
However the N975U was configured for 4G VoLTE already.
On the new N975U1 all I did was plug the N975U sim card in and it was online.
I feel you... this was an unwanted learning curve for me and had me doing a lot of Google searches.
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
Carrier texts should theoretically still work as they are "data". It's the "voice" part of VoLTE that won't work. That's why I can still receive carrier texts on my Galaxy Note 9 with AT&T -- which still has older firmware (so I can be rooted). A few months ago, I lost the ability to make/receive phone calls on my AT&T number when 3G towers were decommissioned in my area... But luckily I have Google Voice number, which also uses "data" (VoIP) so I make/receive all my Google Voice phone calls. (That's been my main phone number for years.)
However, I no longer can make/receive AT&T phone number calls -- which is fine. I switched Google Voice settings to data/Wi-Fi only instead of piggy backing on carrier phone number. Yet, I still receive AT&T texts, which is good because my bank insists on using a "real" (carrier) phone number for SMS security code confirmation.
Amer28 said:
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Click to expand...
Click to collapse
You are in Portland? What carrier are you using that still has 2G and Edge?
ChazzMatt said:
You are in Portland? What carrier are you using that still has 2G and Edge?
Click to expand...
Click to collapse
I'm with a company that uses T-Mobile towers. I connect just fine with 4G LTE, and get reasonably good speeds over it. But when I'm on 4G, I cannot make or receive calls or text. It says Emergency Calls Only.
So far, I've tried everything. I resettled network. I looked for different APN values that may fix the issue. When I couldn't think of anything else, I did a factory reset. (I mean, I wiped Data, and all other partitions in TWRP except for System and SD Card.) There have been no changes.
I'm starting to think the issue may be hardware, I did drop the phone a couple of times the day it stopped working. Though I usually end up dropping the phone once a day or every two days. I can't believe the screen hasn't cracked yet, at all. Could a drop from 3-4 feet on hard surface like tiles damage the antenna in such a way that only 4G data works?
I'm ready to give up and buy a new phone even though I can't really afford it. It would be awesome if I can get this to work.
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
I want to also mention that my carrier website has been talking about a data migration that would affect phones using their old SIM Card.
When I saw that, I called them and had them send me a new SIM. I thought surely this must be it, but the new SIM works exactly like the old one.
Perhaps the migration or whatever it is they did that required new SIM cards just doesn't work well with my phone? Even though, before putting the order in, the rep I spoke to did check my IMEI and said that my phone is compatible.
Agreed, it doesn't sound like an IMEI issue.
FWIW, I showed a 4G connection on a phone (I don't remember if it was my V30 or a Galaxy S10+ that I was going to replace it with). On that phone, at one point, but there was no actual connection. So, the indicators aren't always accurate. That's why I thought maybe the data isn't really working, and if data isn't working then VOLTE won't work... and with many of the carriers switching off non-VOLTE calling, that could kill the ability to make calls?
In your case, you said data worked... but if VOLTE was never enabled, and the carrier dropped non-VOLTE, then, again, you may lose calling.
In any case, these were my theories. I think you're on top of the situation but I don't have any other ideas for you to try...
Instead of buying a new phone, have you considered installing and setting up Google Voice, as ChazzMatt said? I recently had to do that because AT&T's 3G shutdown meant that I could no longer place or receive calls. My quick guide on doing that is here: https://forum.xda-developers.com/t/...-based-custom-roms-when.4138223/post-87342453
I don't know why you can't also send or receive texts, but the Google Voice app has the ability to do that, so maybe try using that after you've set it up.
Amer28 said:
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
Click to expand...
Click to collapse
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
ChazzMatt said:
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
Click to expand...
Click to collapse
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Amer28 said:
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Click to expand...
Click to collapse
tried a rom on a j7 2015 because android 6 is going to be left and I only get emergency calls on lte and on 3g, no problem. It's not imei problem maybe exynos processor. I went back to 6.0.1 and no problem with 4g lite. By the way, I'm not in the USA.