Related
Hey,
So I've noticed an issue with my LTE connection, and I couldn't find a similar issue on XDA:
Sometimes, I'll randomly drop from LTE to 4G, and cannot get LTE back unless I cycle through airplane mode or restart my phone.
This happens on more than one occasion:
1. I'll go into CALL SETTINGS, and when my phone checks the network, I lose LTE and stay on 4G.
2. I'm coming out of an elevator, and I'll drop from LTE to 4G.
I've tried reaching out to Samsung and AT&T, but both blame the other (go figure). Since my phone is still under manufacturer warranty, Samsung said they'll repair it. However, I've heard some bad reviews from you and elsewhere about manufacturer's repairs, and I'm not so sure if that's the best solution to ship my phone out to them.
This phone isn't rooted or unlocked - nor has it ever been.
I'd love to hear your thoughts. Has this happened to you? Do you know of this issue? Any possible solutions other than shipping to Samsung?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I really hope I'm not the only one having this issue
att should do a warrent replacement call them or go to a att service center
mavverick said:
I really hope I'm not the only one having this issue
Click to expand...
Click to collapse
Sorry you're having an issue with lte. I don't know of a fix for ya. But I have some last ditch efforts to go thru before you send it away.
1. Open settings -more networks -mobile networks -access point names. Make sure "ATT Phone" is enabled, and verify it's apn settings with your carrier.
2. Find another person on same network as you and compare if lte drops at same time.
3. Request a new sim card from carrier. They are free and only takes a few minutes to swap. You can walk into the store, or request one online.
4. Perform a factory data reset. See if anything improves. You'll need to do this anyway before you send it off. Don't forget to back it up first! Use kies, or your favorite app.
Hey,
I verified my APN settings, tried a new SIM card, and even factory-reset my Note 3. None of those worked. However...
I ended up taking the device to an AT&T Device Support Center, and got it replaced in 15 minutes! The tech there agreed with me that there was nothing else they could do except replace the device. Since my Note 3 was still under the original manufacturer's warranty, AT&T replaced it in minutes - no questions asked.
Now my phone is running perfectly. No dropped LTE!
Glad to hear you got a replacement! Thanks for reporting back.
So as of saturday my unlocked TMobile Note 4 stopped working as a phone, and won't let me make calls.
Information:
-Was on Dr. Ketan L3 version of his rom when it stopped working
-Using the N910T on AT&T
-IMEI is fine and not damaged, both numbers match (using *#06#)
-It shows bars, but when I go to make a call "Not Registered On Network"
What I've Done:
-Flashed Stock Firmware via Odin (Autoboot, and F.Time Rest checked)
-Factory Reset after odin flash
-Checked APN
-Set on LTE/WCDMA/GSM
-Searched for Networks, finds them, but when I choose AT&T it takes forever and then finally kicks me out and then in notifications, I get the "Not Registered to Network"
-Did the remove the battery thing, and removed sim
-Went to AT&T and got a new sim, worked for 1hr (sporadically) and then went back to "Not Registered on Network"
-At the store I was on phone with AT&T tech trying to troubleshoot the problem and that is when it was working shortly
-Called T-Mobile and checked to see if they blocked my IMEI number, nope they didn't, couldn't help me out further than that
-AT&T was showing that it was a Note 4 so not having that coming up as a Blackberry issue that some reported, so that's not it
-*#0011# shows service limited, but it is unlocked and everything is fine, the IMEI is good, and all is well but the limited service
-Put it in Airplane mode and woke it back from there after 5+minutes
-cleaned the connectors on the sim (new sim anyways so shouldn't really need them)
I'm running out of options, the only thing I can think of being the problem is that I might have started out using this phone on COD2, and when I flashed a COG2 firmware it didn't like that and so my phone's account settings didn't fully transfer.
Also I was messing around with the bands settings (*#2263#) what should they be on? Automatic, LTE/GSM only, or what?
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
kabuk1 said:
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
Click to expand...
Click to collapse
Thanks, yeah it kicks in randomly for like a minute and then dies, I take it to my parent's house (about 10 miles away) and along the way I get a good signal, but then when I reach their house, back to nothing. I was using it just fine the week prior. I partially blame Dr. Ketan, ever since installing his rom, I had multiple issues. I since uninstalled it and tried going back to stock. Any idea on what a good "safe" band setting is? I have that settings set to automatic, but if there was a good "safe" band that would be great. A common LTE tower. Even when I do connect or get connected, I can't register on that network, my phone won't let me. I've tried that. The bars drop to zero. I damaged my antenna wire (white one) and I just replaced it with a new one I purchased, but the hacked together one seemed to be doing the same quality job as the new one is. It shows the signal, but as soon as you try tying it down to a network it rejects it. I was afraid that when I flashed the stock image via odin it removed the unlock, but it was still there. I just hate that now I have a $500 pda, when it was a phone and now i'm relegated to using a f*ing flip phone.
i think your antenna cable is damaged. the only way to know that is be close to a tower, and see if your work or not.
bought and replaced with new ones, I get full bars, in my bedroom, but apparently they're tied to Tmobile since when I try to register it to AT&T they magically disappear, but when I close the app, they come back at the same strength level. I can't register them to Tmo since the sim. Yet my phone is telling me it's unlocked (*#0011#), IMEI = PASS, 1;
I think the prob is due to the different frequencies.
Your baseband would not be tied to a rom(ie Dr Ketan) Unless that rom contains Modem.bin
Your apn needs to be att if that's your Sim obviously.
International version has a different chipset. .. I know it's not your case. .
But it's open to any Sim. ..
I can say this.. I have a N2 unlocked (tmob) I run an Att Sim it works but the sig is really spotty... COD6/ COG2 may not be lining up frequency wise with your att Sim. ..
Try rolling your baseband back even further. .
Flashvetrin
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
dcoke said:
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
Click to expand...
Click to collapse
Well I would think automatic is out for sure.. the other prob would be after reboot the chipset will search for the default.. but I could be wrong.
I do not know what the numbers would be for band identification.
You may get lucky when calling Att and ask for someone in a higher tier. To give you some numbers for frequincies .
But you have ruled out hardware correct??
By putting a tmob Sim in????
Cuz I know you posted you did antenna work..
And I do know you said you get bars then it fades..
The fact it fades and doesn't lock into even a G band for example. Just leads me to believe the apn can't lock down based on the frequincie and the built in lte chipset...
It would be nice to just flash an att modem wouldn't it?? But don't even think about it.. lol you'll soft brick..
I wish I had a better solid answer you. You may just start testing those different bands and see if you get closer to a lock.
Flashvetrin
U rock, lol. Thx man
My Tricked Out N910P
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
dcoke said:
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
Click to expand...
Click to collapse
Heres
A simple method for COD6
And try odin 3.07
I need to think about this some more and get back to you...
This is a partial firmware.. it consists of the modem and bootloader COD6.
Also to rule out damage if you can get a T Mobile Sim put it in the device and see if it locks down a signal....
Flashvetrin
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
dcoke said:
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
Click to expand...
Click to collapse
You are the first of this kind that I'm aware of.. in regards to this issue..
Make sure you read the detail in if your device bootloops, to reboot recovery and flash the Rom.. if you want flash the Rom in the op that I've linked you to.
Wipe sys/dal/cach/data..
And flash it can't hurt.. [emoji16]
I really hope a Tmob Sim and or COD6 gives you results...and good ones at that.. [emoji2] [emoji106]
Flashvetrin
Got the sim card, $65 for that crap, and it didn't work. Called T Mobile customer service, explained my situation and how I was calling on another phone on another carrier and they insisted on calling me back on the broken not working phone. I guess I'm just screwed, and lost $500, which like I said, I can't afford to have. It's just so frustrating. I also tried the COD6 partial firmware, and nothing there also. I'll try t-mobile again. The only and last option I have, if possible, is to try to relock my phone and re-unlock it since there isn't any real way to tell if my GSM is damaged. I think my unlocked status got damaged when my phone upgraded to COG2, and since it's in that weird limbo state I can't use my phone. Do you know how to relock it?
Edit: When I look at my IMEI Number through *#06# it shows that the last two digits (independent of the actual IMEI number, since that matches everywhere) to the right of the "/" as 14, yet through "about device" it shows my imei version as 10. I assume that the 14 in the "06" screen is the version it's reading off the phone, could that be causing the issue? How would you even fix that? I don't know. but thanks again, you've been helpful.
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
HueyT said:
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I'm already unlocked, rooted, TWRP'd and using the PureNexus that came out end of april (I haven't flashed the one in may yet). I believe I'm also currently using the latest radio and latest bootloader.
Edit - I actually was not on the most recent radio, but I did flash that, no change.
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
In others countries we don't get the same bands management, then I can't say anything about LTE.
But I'm on PureNexus 7.1.1 and I get the same "issue" about network droppin when calling. When the call starts, my phone turns into don't disturb-mode and recover the network only when the phone call ends.. It doesn't really cut my network connection, but it looks like. It may be rom settings.
However I don't care as long as everything works good, it's just an icon. (how a phone call can be done while network is shutted off ^^)
When I was on the stock ROM, this autumn, 7.1 version of Android did the same thing, loosing data connection while being still connected to the network (but at anytime not just phonecalls). Finding it back some minutes later. That was fixed with 7.1.1. Stock.
Hope that might help you (looks not ) if it's the same problem. May be give an eye to the Rom settings..
Have you tried if your device do the same thing with an another Rom ? (stock for example)
Larzzzz82 said:
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Click to expand...
Click to collapse
I knew something looked like it was missing. I don't have any enhanced 4g LTE settings in that section. Normally there's a tick box to turn it on there. It's missing. Is that due to them not having it turned on in my account?
Also for everyone else, this problem only started when I tried the whole at&t switch. I was on this rom when I switched and it worked fine before then. I didn't factory reset since then though, wondering if I need to try that.
zelendel said:
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Click to expand...
Click to collapse
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
BlockOfDynamite said:
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
Click to expand...
Click to collapse
I think i'm going to reflash my rom today. I did the modem, twrp is up to date, bootloader is fine. I did the reset network settings (I was sure that was going to fix it, no dice). So I'm going to reflash the rom today and see if that fixes it. After that I have no idea what is left to try other than reverting to stock, which I'd like to avoid.
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Larzzzz82 said:
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Click to expand...
Click to collapse
How do you enter the hidden menu on the n6? I thought I found it but it wasn't working.
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Larzzzz82 said:
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Click to expand...
Click to collapse
I got in, VoLTE was not ticked. I ticked it. I got the setting for it then in settings. But making a phone call gave me an error. I rebooted, and it's not ticked now. So does that mean I need to call Verizon to have them flag my account?
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Larzzzz82 said:
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Click to expand...
Click to collapse
That did the trick. All fixed. Thank you! That was driving me nuts. I never considered the idea that the setting would be turned off . But since I did leave and come back...
Thanks again!
Glad you're all set. ?
I recently bought an unlocked Galaxy S10 SM-G973U on Amazon. Got new SIM card from a Verizon MVNO and activated phone. The phone downloaded Android 12, One UI version 4.0. Firmware Build number SP1A210812.016.G973USQS6HVA1. Service provide Software version SAOMC_SM-G973U_OYN_SPR_12_0007 SPR/XAA/VZW. The problem is there is no menu option to activate/switch on VoLTE which means when I'm on a call there is no internet. I've talked to the MVNO tech support multiple times and was told they couldn't see any problems on their side, or that the SM-G973U does not support VoLTE which is not true. I found on one of AT&T's sites that the SM-G973U needs a software patch to enable VoLTE. I also found a couple of USSD codes but they either didn't work or didn't get me to the right setup screen to turn on VoLTE. I even stopped by a Samsung store and they weren't any help either. They said they could re-flash a stock firmware but it would revert to being locked to a carrier which is apparently also not true based on what I've read on this forum. Anyone know how I can turn on VoLTE or know of an apk file or software patch to enable VoLTE?? Does one of the firmware versions posted online have the patch to turn on VoLTE??
I think the issue is that your phone is showing SPR/XAA/VZW. You say you're on a verizon MVNO (who, by the way?)... but your phone isn't seeing that. It's actually saying it's active for SPRint. The second one, XAA, means it's not able to detect the SIM type... and the third was that it was originally VZW, which you can't change and isn't really relevant. (That's just what the phone was "born" as).
Bottom line, your phone isn't seeing VZW or an MVNO as the active CSC nor the SIM card. In the past, the easy thing was to change the CSC to what you need, but I haven't found a way to do that actively. What's supposed to happen is that the CSC should update based on the SIM card and cell signal you're getting... but this doesn't always happen. I bought two phones - one switched with no issues, the other I could not get it to change no matter what I tried.
That said, the easiest thing is to clean flash the phone with ODIN to a VZW or your MVNO's ROM, so that (hopefully) the CSC updates automatically. You could also consider flashing a U1 (unlocked) ROM, as yours is not technically an unlocked ROM (U means it's a carrier ROM... which may be why it's not switching over?)
Again, I tried all of these on the second phone I bought, and nothing would switch it (my carrier is Total Wireless, which is a VZ MVNO, and actually shows up as Tracfone (TFN). I had to return that second phone and get another with TFN already activated, and that worked fine... so be sure you do this before you drop out of your return period.
Bottom line, you should be able to get this all working... my VOLTE/VOWIFI works fine... just a matter of getting you there.
Thanks. My carrier is Straight Talk which is now VZ. The SIM card they sent me has the wording "Verizon Compatible" written on it. I finally found a document that explains how to interpret the CSC codes and your explanation clarifies my understanding of it. Sound like I'll have to re-flash it. Since it was originally a VZW phone I'm thinking I should flash it back to VZW to see if that works before trying U1.
Dumb question as this is my first time flashing a phone. (I've flashed quite a few other things but never had to worry about CSC codes and bootloader versions, etc.) I don't see VZW firmware on samfirms or sammobile. I see Sprint, T-Mobile, and one listed as USA without carrier info but I don't see one for VZW. Can someone point me to the correct location to download SM-g973U and U1 firmware for VZW? Greatly appreciated and thanks for putting up with my lack of knowledge!
Edited: Found the files on sammobile. Will try the U1 (VZW) first. I'll keep my fingers crossed.
schwinn8 said:
I think the issue is that your phone is showing SPR/XAA/VZW. You say you're on a verizon MVNO (who, by the way?)... but your phone isn't seeing that. It's actually saying it's active for SPRint. The second one, XAA, means it's not able to detect the SIM type... and the third was that it was originally VZW, which you can't change and isn't really relevant. (That's just what the phone was "born" as).
Bottom line, your phone isn't seeing VZW or an MVNO as the active CSC nor the SIM card. In the past, the easy thing was to change the CSC to what you need, but I haven't found a way to do that actively. What's supposed to happen is that the CSC should update based on the SIM card and cell signal you're getting... but this doesn't always happen. I bought two phones - one switched with no issues, the other I could not get it to change no matter what I tried.
That said, the easiest thing is to clean flash the phone with ODIN to a VZW or your MVNO's ROM, so that (hopefully) the CSC updates automatically. You could also consider flashing a U1 (unlocked) ROM, as yours is not technically an unlocked ROM (U means it's a carrier ROM... which may be why it's not switching over?)
Again, I tried all of these on the second phone I bought, and nothing would switch it (my carrier is Total Wireless, which is a VZ MVNO, and actually shows up as Tracfone (TFN). I had to return that second phone and get another with TFN already activated, and that worked fine... so be sure you do this before you drop out of your return period.
Bottom line, you should be able to get this all working... my VOLTE/VOWIFI works fine... just a matter of getting you there.
Click to expand...
Click to collapse
Success! Was able to flash U1. VoLTE is now working. The CSC now shows TFN/TFN/VZW. Much appreciated!!!
Awesome, glad to hear that fixed it easily!
And TFN... I'm a fan there, too!
Hi! I'm having a similar issue with the same model and happy to see someone was able to enable VoLTE. However, most of what you said above is a foreign language to me. Would one of you be willing to give me a crash course in what you did?
Here's my specific situation. Last week (~1/4/23) Tracfone shutdown 3G. My Samsung Galaxy S10 (SM-G973U) says my network is set to LTE/3G/2G. I've read LTE is 4G, but still can't make or receive calls/texts, but data and 911 calls still work. Their tech support is no help.
From reading online it sounds like I may need VoLTE, not just LTE. Hence finding this thread. If one of you would be willing to spare some time to walk me through what you did I'd really appreciate it. In the mean time I'll try to figure out what "flashing" mean in a context that doesn't involve showing body parts
Thank you in advance!!
I'm on Tracfone (they were bought out by Verizon, BTW) - I was on Total Wireless before, which is now Total by Verizon. You might try contacting support again, as they are now VZ, and may have more help to offer.
My S10+ is running 975U1 now, and it works for VOLTE/VOWIFI properly. You may consider getting a U1 ROM installed, and maybe even the VZW (or TFN) version if available - that may get you working.
Did VOLTE ever work for you before on this or any other carrier? What is your CSC right now?
schwinn8 said:
I'm on Tracfone (they were bought out by Verizon, BTW) - I was on Total Wireless before, which is now Total by Verizon. You might try contacting support again, as they are now VZ, and may have more help to offer.
My S10+ is running 975U1 now, and it works for VOLTE/VOWIFI properly. You may consider getting a U1 ROM installed, and maybe even the VZW (or TFN) version if available - that may get you working.
Did VOLTE ever work for you before on this or any other carrier? What is your CSC right now?
Click to expand...
Click to collapse
Thanks for replying! I'm not entirely sure if VoLTE has worked previously. I bought this phone 6/2021 and have only haver had tracfone service for it. I did find in my setting that VoLTE calling is set to on so it seems like it should work. Of note, the 4Glte in my status bar has always been grayed out (I went back and looked at some old screenshots).
My current CSC is VZW/XAA/ATT.
I spoke with tracfone customer service yesterday and they had me reset my network setting and now I don't even have data and the 4Glte in my status bar that was previously gray has now completely disappeared.
Their customer service refuses to talk to me now (literally no one answers when it transfers to an agent) or they hang up on me, and no I haven't been rude, but I have told them I'm recording the call.
I bought a mint mobile package last night because I'm beyond frustrated with Tracfone. I'm worried I'll have the same problems with Mint. I'm not sure if my settings are screwed up or if it's just Tracfone. In any case things are worse now after talking to customer service yesterday.
I also notice there was no APN setting on my phone so I updated it today and restarted but no difference.
Thanks for any input!! Much appreciated. Sorry for the novel.
Ok, so based on your CSC, the phone is not seeing the SIM's carrier - it's showing XAA which means it's using the default settings, which is probably why your not getting VOLTE. The active CSC of "VZW" may be ok... depends on which carrier you're on with Tracfone. I think they're VZW only, but I'm not completely sure.
You may want to just get a new SIM card and get that activated. HOWEVER, the problem you'll likely face is that the phone was born ATT (last CSC). This means the IMEI won't match a "compatible" phone to Verizon, and they will flat out refuse to activate it (even though WE al know it will work fine). If you still want to do that, you will have to activate the new SIM on a VZ "compatible" phone, then you can swap it to the S10. Note that VZ complains about this when you talk to them... so don't tell them you're doing this... but I've done it many times and it works fine.
If your actual behind-the-scenes carrier is ATT, then you can do the activation with your phone without issue.
If none of this works for you, you can switch carriers to an ATT MVNO and you should be good to go.
schwinn8 said:
Ok, so based on your CSC, the phone is not seeing the SIM's carrier - it's showing XAA which means it's using the default settings, which is probably why your not getting VOLTE. The active CSC of "VZW" may be ok... depends on which carrier you're on with Tracfone. I think they're VZW only, but I'm not completely sure.
You may want to just get a new SIM card and get that activated. HOWEVER, the problem you'll likely face is that the phone was born ATT (last CSC). This means the IMEI won't match a "compatible" phone to Verizon, and they will flat out refuse to activate it (even though WE al know it will work fine). If you still want to do that, you will have to activate the new SIM on a VZ "compatible" phone, then you can swap it to the S10. Note that VZ complains about this when you talk to them... so don't tell them you're doing this... but I've done it many times and it works fine.
If your actual behind-the-scenes carrier is ATT, then you can do the activation with your phone without issue.
If none of this works for you, you can switch carriers to an ATT MVNO and you should be good to go.
Click to expand...
Click to collapse
OK some of that was still over my head. I'll see what happens with the Mint Sim... one f/u question now though. You said the ATT means my phone was "born" ATT. I bought my phone off backmarket and it was sold as "unlocked". Was that not true? How can I be sure in the future if I buy a used phone that's not from my carrier that it will actually be compatible?
Unlocked just means it's not locked to a carrier. That is true in your case, otherwise you wouldn't have been able to install ANY non-ATT SIM. So, you did the right thing to get an unlocked phone, and that is what you got.
The issue with compatibility is just the asshole carriers spreading lies. They do this to try to get people to buy THEIR phones, for no reason other than to make money and confuse consumers. The "born" CSC has no bearing on anything, really... neither does the carrier-specified IMEI. In your case, the XAA is good, which means it's a multi-carrier ROM, which works with all USA carriers.
Mint is a good idea - being an ATT carrier (IIRC), that should work and they should help you get it up and running even if they have to activate it. Good luck!
Awesome! Fingers crossed!! Thank you for your time and all the info❣
I'll try to remember to give an update in a few weeks for future readers
Goldie8709 said:
Awesome! Fingers crossed!! Thank you for your time and all the info❣
I'll try to remember to give an update in a few weeks for future readers
Click to expand...
Click to collapse
UPDATE: Switching to Mint worked like a charm! Once my number ported and I put the new SIM card in, service was instantaneous! I've had Mint for 3 weeks now and the service is so much better than with Tracfone! My calls go through nearly as soon as I hit call, the internet is faster.
I didn't need to do a thing either. No making APN settings, etc. I'm betting it has to do with what you said about my phone being born ATT. So funny because the software(?) is Verizon - shows the Verizon when I restart/power up. I still love my bastard phone
So thankful I didn't buy a different phone!!! Again thanks for all your help @schwinn8
Thanks for reporting back and letting us all know, and I'm glad it worked out well!
Yeah, the carriers pull this nonsense all the time... it's BS. The phones are all the same, only the ROM changes. If we can change ROMs (which we can) then there should be no reason to force users to specific IMEIs. But we know why they do this - follow the money. I encourage people to write to the FTC and FCC about this (I have).
I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".
This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.
Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?
Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?
If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?
I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?
Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.
https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.
Seeing this forum has so little activity, on 1/21 I ended up getting a used Moto E6 (XT-2005-3 is a tmobile aka carrier unlocked MetroPCS version). While overall this is not as nice a device and has fewer features than Note 4, it does cover what for me are the essentials - removable battery, SD card slot, support for 5.8GHz wifi. Best of all, it supports B71 which will be helpful for, well, making phone calls!
I still ponder someday getting one of these as a hobby device, but that would be second place to the E6 for use as a phone, and won't be for a couple more months yet (too many expensive household issues are taking their toll on my "toy" budget right now).
ForestCat said:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice.
Click to expand...
Click to collapse
Thank you, this was the part I needed to find out. With that in place, the only thing missing would be the B71 coverage but the E6 is already in place for that.
Re your Verizon adventures, I have no experience with any of that. What I read about T-Mobile dropping support for the verizon version in the last network update is all I know, and I don't have the skills to dispute what they say there. The best I could do is offer some links to threads on this forum but on double checking them it seems you've already been there and got no answers.
The only thing I see that might help you with that is if you could update just the t-mobile modem without disturbing the verizon bootloader. I see you tried that but it didn't stick when using Odin. I don't know if it would be any different using SmartSwitch that seemed to work for MarineWonder as he posted at https://forum.xda-developers.com/t/...pgrade-on-jan-29th-2021.4224237/post-87464609 ?
Then again he may have been putting it on a t-mobile phone rather than mixing with the verizon bootloader so who knows?
My guess since it has been so problematic for you on the verizon phone is that you may need to only use a tmobile phone since that may be the only way to get the last t-mobile modem update. Bummer that the one you bought has a dead usb port. How are you charging it? Is there any chance you could return it to the seller since it came pre-broken? Then put the refund money toward another, hopefully working, tmobile phone? And would that MODestROM work on a non-verizon phone?
The only other thought I had is there are apps to connect to ADB over wifi. Sadly most of these need root. The ones that don't, seem to need at least once using a usb connection to do the "adb tcpip 5555" command to set it all up. . . . how annoying that it is all so circular!
There is also https://telnetd.en.aptoide.com/app?store_name=apps&app_id=59202144 , maybe a telnet connection could do the "adb tcpip 5555" command instead of using the USB connection? Sadly the documentation (at https://waxrain.com/docs/010.html ) appears to be written in Chinese, and I never had much luck with google translate.
The N910T still supports VoLte.. It is still compatible with cellular networks.