SM-N910T on T-Mobile USA in 2023? - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

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.

Related

N900A, T-Mobile ROM, and WiFi Calling/SMS...

Hello,
I just retired my venerable Samsung T699 Relay 4G (RIP QWERTY Keyboard) and, just picked up an unlocked, "refurbished" AT&T Note 3 for pretty cheap (it was sold as an "International" model, so I didn't know it was an AT&T version until I got it). I've had T-Mobile service for the last couple of years, and the big draw, for me, is WiFi calling/SMS; I've installed SafeStrap and been trying some T-Mobile ROMs, but can't seem to get WiFi calling to work. Obviously I've got a T-Mobile SIM card, and I've tried changing/adding APNs, and installing different builds of KitKat (some of which won't even boot - NB4 and NF9 seem to work best), but I still can't get it to work properly. I've been racking my brain and searching the Interspace for the last two weeks with no luck... what am I missing? Is it even possible?
Thanks in advance!
Hello,
As a fellow N900A user on Tmobile, I have been trying to get wifi calling as well.
I tried using a tmobile stock rom with wifi calling baked in (tweaked), but that did not work. I was told that I need to add an emergency 911 address, but even doing this did not do it.
I would think that wifi calling is doable, but something tells me that tmobile might be doing something similar to Verizon. Rumor was that Verizon had a list of IMEIs, and if your IMEI was not on their list, you couldn't bring the phone over to Verizon, even if it were CDMA capable (once again, this is rumor as I cannot confirm this is true).
The closest I have been to getting wifi calling through tmobile was having the settings show on the stock tmobile rom, but that was about it. Maybe someone in the forums has an answer/got it working, but I have yet to see one. I'll keep you posted if I somehow get it to work, but something tells me this won't happen for a while.
AresRising said:
Hello,
I just retired my venerable Samsung T699 Relay 4G (RIP QWERTY Keyboard) and, just picked up an unlocked, "refurbished" AT&T Note 3 for pretty cheap (it was sold as an "International" model, so I didn't know it was an AT&T version until I got it). I've had T-Mobile service for the last couple of years, and the big draw, for me, is WiFi calling/SMS; I've installed SafeStrap and been trying some T-Mobile ROMs, but can't seem to get WiFi calling to work. Obviously I've got a T-Mobile SIM card, and I've tried changing/adding APNs, and installing different builds of KitKat (some of which won't even boot - NB4 and NF9 seem to work best), but I still can't get it to work properly. I've been racking my brain and searching the Interspace for the last two weeks with no luck... what am I missing? Is it even possible?
Thanks in advance!
Click to expand...
Click to collapse
gangpe said:
Hello,
As a fellow N900A user on Tmobile, I have been trying to get wifi calling as well.
I tried using a tmobile stock rom with wifi calling baked in (tweaked), but that did not work. I was told that I need to add an emergency 911 address, but even doing this did not do it.
I would think that wifi calling is doable, but something tells me that tmobile might be doing something similar to Verizon. Rumor was that Verizon had a list of IMEIs, and if your IMEI was not on their list, you couldn't bring the phone over to Verizon, even if it were CDMA capable (once again, this is rumor as I cannot confirm this is true).
The closest I have been to getting wifi calling through tmobile was having the settings show on the stock tmobile rom, but that was about it. Maybe someone in the forums has an answer/got it working, but I have yet to see one. I'll keep you posted if I somehow get it to work, but something tells me this won't happen for a while.
Click to expand...
Click to collapse
Yeah, considering I have zero service with any provider where I live (but 4G LTE 100 yards down the street), WiFi services were the single reason I went with T-Mobile. Considering the Unlocking Bill, one wouldn't think a carrier could block IMEIs from being used on another carrier... but I have a hard time reading the fine print, so there is that.
I've tried several of the stock T-Mobile ROMs, and while WiFi calling was there, it simply wouldn't enable; it would try to enable, but never would. Have you contacted T-Mobile and asked if there are any potential fixes? I'm considering doing that, but am worried that they'll say "Oh, that's your IMEI, looks like you can't use it on our network SORRYABOUTYOURLUCK!"
I have contacted tmobile about this before.
Their response was that they did not know why it did not work. They helped me set up the emergency 911 address, but they said when it comes to other hardware they couldn't give me a reason why it wouldn't work.
I remember dwetherill (sp?) mention that some n900a users were able to get wifi calling on their phones. I don't know if the modem can/will affect wifi calling, but at this point it's the easier thing to test.
I'm on the NJ5 modem - I might try testing out NC2.
Have you tried carl's TMB version of the norma stable rom? Check it out if you haven't. Wifi calling is supposed to connect automatically. I haven't seen it work yet, but I'll keep you posted if somehow I get it to work.
AresRising said:
Yeah, considering I have zero service with any provider where I live (but 4G LTE 100 yards down the street), WiFi services were the single reason I went with T-Mobile. Considering the Unlocking Bill, one wouldn't think a carrier could block IMEIs from being used on another carrier... but I have a hard time reading the fine print, so there is that.
I've tried several of the stock T-Mobile ROMs, and while WiFi calling was there, it simply wouldn't enable; it would try to enable, but never would. Have you contacted T-Mobile and asked if there are any potential fixes? I'm considering doing that, but am worried that they'll say "Oh, that's your IMEI, looks like you can't use it on our network SORRYABOUTYOURLUCK!"
Click to expand...
Click to collapse
gangpe said:
I have contacted tmobile about this before.
Their response was that they did not know why it did not work. They helped me set up the emergency 911 address, but they said when it comes to other hardware they couldn't give me a reason why it wouldn't work.
I remember dwetherill (sp?) mention that some n900a users were able to get wifi calling on their phones. I don't know if the modem can/will affect wifi calling, but at this point it's the easier thing to test.
I'm on the NJ5 modem - I might try testing out NC2.
Have you tried carl's TMB version of the norma stable rom? Check it out if you haven't. Wifi calling is supposed to connect automatically. I haven't seen it work yet, but I'll keep you posted if somehow I get it to work.
Click to expand...
Click to collapse
I'm on NC2, and haven't gotten anything to work as of yet... I've been looking for modem threads, but I guess I need to look a little harder. I'll search that ROM out and give it a shot, and let you know if it works with NC2. Thanks for the heads-up! :good:
So I tried NC2 modem, and it is not allowing for wifi calling.
I went to tmobile yesterday to get another line added. Rumor on the tmobile side is that AT&T is working to get wifi calling setup for the n900a's by around April. Take it as a rumor at this point, seeing how it came from tmobile, but the rep made a good point - AT&T tends to follow what tmobile is doing, so who knows.
Here's to hoping they're right.
BTW, I went to the note 4 tmobile forums, and I grabbed a deodexed stock rom. I noticed that there were a few files related to wifi calling (had WFC in the name). I tried playing around with it last night, and I managed to get the settings. It will even go so far as to turn the phone GSM radio off when you select wifi only. It's doing what Tweaked was doing for me (which was keeping the wifi calling option grayed out (enabling). I think I'm still missing a few files to get it to work, but I'll keep playing around with it later and let you know if I have any success.
AresRising said:
I'm on NC2, and haven't gotten anything to work as of yet... I've been looking for modem threads, but I guess I need to look a little harder. I'll search that ROM out and give it a shot, and let you know if it works with NC2. Thanks for the heads-up! :good:
Click to expand...
Click to collapse
gangpe said:
So I tried NC2 modem, and it is not allowing for wifi calling.
I went to tmobile yesterday to get another line added. Rumor on the tmobile side is that AT&T is working to get wifi calling setup for the n900a's by around April. Take it as a rumor at this point, seeing how it came from tmobile, but the rep made a good point - AT&T tends to follow what tmobile is doing, so who knows.
Here's to hoping they're right.
BTW, I went to the note 4 tmobile forums, and I grabbed a deodexed stock rom. I noticed that there were a few files related to wifi calling (had WFC in the name). I tried playing around with it last night, and I managed to get the settings. It will even go so far as to turn the phone GSM radio off when you select wifi only. It's doing what Tweaked was doing for me (which was keeping the wifi calling option grayed out (enabling). I think I'm still missing a few files to get it to work, but I'll keep playing around with it later and let you know if I have any success.
Click to expand...
Click to collapse
I wonder how that would work regarding using a T-Mobile SIM in the AT&T phone, and if it could support cross-carrier features like that.
You're a braver soul than I, that's for sure. If I knew anything about what I was looking at/for, I'd be more than willing to help get this nut cracked... otherwise, I look forward to your findings!

How do you fix Not Registered On Network?

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.

CDMA Workshop alternatives and can I get data on other carriers?

So, I've recently rooted and unlocked my device and I wanted to know if I can bring it to another carrier and still get data.? I'm using the LS991 Sprint version. I also wanted to know if there are any good CDMA Workshop alternatives; it's really expensive and I'm only gonna be using on a few devices.
Dfs
So you rooted (doesn't really matter with respect to carrier support) and you unlocked it (that's what matters with respect to carrier support) - so you put in a SIM card for the carrier you want, set the APN data (use Shortcut Master if needed, there's a version specifically modded for the LS991 directly available in my post HERE - might be a good idea to read that post as well since that's what I did myself.
Worse comes to worse if you have no luck because you unlocked your LS991, consider installing the global LS991 ROM (whether it's Lollipop ZV6 or Marshmallow ZV9 or ZVA - if you install ZVB you can never go back to anything prior so be aware of that) which will work much better for other carriers than using the unlock mod so many of us have done in the past.
Hindsight being what it is, if I knew about the global ROM when I got this G4 recently I wouldn't have mucked around with all the unlocking crap and the carrier partition at all for any reason because just installing the global ROM (or modifying build.prop to allow for global unlocked operation) is way more useful and less damaging to the phone. Modifying the build.prop isn't necessarily a cakewalk but, since someone else has already done it for others and posted the global ROM(s) for Lollipop and Marshmallow (as .img files you flash using the Send_Command.exe/dd method) it's really not a big thing anymore.
If you muck up flashing an .img file you can typically just use LGUP and a TOT file to get things working again so it's relatively safe overall, but if you muck up the unlock and trash the carrier partition content the phone will end up being pretty much useless unless you have that information safely backed up someplace (I'd say multiple backups in multiple locations, to be honest).
Anyway, if you truly want the phone to be capable of working on other carriers, my suggestion is go for the global ROM but that's just my own personal opinion on the matter. I'm using tabp0le's MellowMallow ZVB global ROM on my LS991 and T-Mobile LTE works just fine for me, for the record. It did take a little work - I wrote about how I got the full phone/data working in that post with Shortcut Master - but it does work.
Thanks for the help!
One last question, how did you get other carriers to let you activate the phone? Everytime I try they ask me imei then tell me my phone won't work on their network.
Well I've had service with T-Mobile in the past (not currently but will again soon), I have a bunch of T-Mobile microSIM cards because whenever they put the SIM card activation kits on sale for $.99 or sometimes even free (rare but it happens) I usually grab 3 at a time so I have 'em around for testing purposes. T-Mobile doesn't require me to provide any info to them, and even if I go to their website right now and input my IMEI number it'll say it's not recognized, etc but it's not relevant: it works, and that's what matters.
Most carriers don't actually require you to provide the IMEI for any reason as long as you can get one of their microSIM cards (or nanoSIM with adapter) and then get service without having to contact them. T-Mobile is somewhat unique in that process I suppose. With this SIM card I have (it's never been activated) I can go to their website and sign up for service right now and it'll be active in 10 minutes or less, sometimes when I've activated service (it's prepaid so I don't necessarily keep it month to month, sometimes I choose some other service for testing) it's done before I even sign out of their website, like 30 seconds or less and wham, the phone beeps telling me service is working.
So, the advice is: get a SIM card for the phone from the carrier you're interested in and go from there, not sure what else to suggest honestly.
br0adband said:
Well I've had service with T-Mobile in the past (not currently but will again soon), I have a bunch of T-Mobile microSIM cards because whenever they put the SIM card activation kits on sale for $.99 or sometimes even free (rare but it happens) I usually grab 3 at a time so I have 'em around for testing purposes. T-Mobile doesn't require me to provide any info to them, and even if I go to their website right now and input my IMEI number it'll say it's not recognized, etc but it's not relevant: it works, and that's what matters.
Most carriers don't actually require you to provide the IMEI for any reason as long as you can get one of their microSIM cards (or nanoSIM with adapter) and then get service without having to contact them. T-Mobile is somewhat unique in that process I suppose. With this SIM card I have (it's never been activated) I can go to their website and sign up for service right now and it'll be active in 10 minutes or less, sometimes when I've activated service (it's prepaid so I don't necessarily keep it month to month, sometimes I choose some other service for testing) it's done before I even sign out of their website, like 30 seconds or less and wham, the phone beeps telling me service is working.
So, the advice is: get a SIM card for the phone from the carrier you're interested in and go from there, not sure what else to suggest honestly.
Click to expand...
Click to collapse
You good sir are a god among men, phone and data are working like a charm. Now I can tell sprint to go **** themselves!
glad it worked for you. MY experiences with ls991, i am using it nvmode. zv6 rooted works for me with cdma data. but data doesnt work with zv9 or zva. global rom doesnt work unless, I edit build.prop target carrier to SPR . it is open to use it as global mode. I am using it in cdma nv mode.. not with any sim..
sunilromy said:
glad it worked for you. MY experiences with ls991, i am using it nvmode. zv6 rooted works for me with cdma data. but data doesnt work with zv9 or zva. global rom doesnt work unless, I edit build.prop target carrier to SPR . it is open to use it as global mode. I am using it in cdma nv mode.. not with any sim..
Click to expand...
Click to collapse
so in my case i use att on ls991. my build prop is ruim,sim i believe. now does that sound rite for gsm?
also another cdma workshop alt if qpst i used that one to rebuild my g2 a few years back
TheMadScientist420 said:
so in my case i use att on ls991. my build prop is ruim,sim i believe. now does that sound rite for gsm?
also another cdma workshop alt if qpst i used that one to rebuild my g2 a few years back
Click to expand...
Click to collapse
Ruim is basically used when it comes to cdma sim card.
"Removable User Identity Module (R-UIM) is a card developed for cdmaOne/CDMA2000 ("CDMA") handsets that extends the GSM SIM card to CDMA phones and networks. To work in CDMA networks, the R-UIM contains an early version of the CSIM application."
Your is at&t 4g gsm card. [emoji4]
Check your build.prop and search for
ro.build.target_operator: OPEN
Most probably for global mode open works
For making it work on cdma nv, i have set it to SPR
You can tweak with it by changing to options, it will also change signal bar and 4g symbol like at&t
These will show a Standered international 4G data icon for 3G/HSPA+ and LTE for LTE.
ro.build.target_county: CA
ro.build.target_operator: TLS
These will show a standered international 3G data Icon for 3G/HSPA+ and 4G for LTE (Messes up settings menu pretty bad)
ro.build.target_county: SK
ro.build.target_operator: SKT
If you want the AT&T 4G and 4G LTE Icons.
ro.build.target_county: US
ro.build.target_operator: ATT
Sent from my LGLS991 using Tapatalk
---------- Post added at 02:36 AM ---------- Previous post was at 02:26 AM ----------
My fav cdma tools are qpst, cdma workshop, dfs, revskill and bit advance is qxdm All are freely available. I cant say which one is best hahah. Trust me for me, all of them worked at some instance when i was stuck. Revskill is great with htc finding spc. Though i used dfs mostly.
Sent from my LGLS991 using Tapatalk

Anyone else on Sprint? No APN settings?

Anyone else running the G5S+ on Sprint? It's working fairly well for me other than a couple of IPv6/IPv4 connection issues. However, is it normal for Cellular network settings to not include any kind of APN settings/options? We have six different devices on our family Sprint account -- Nexus 6, Samsung Galaxy S5 Active, Samsung Galaxy S3, iPhone 7, iPhone 6+, and now the G5S+. All of the other devices have a way to edit the APN settings, even when running the stock, unrooted ROM. I'm waiting to root my G5S+ until after an official Oreo update. Is this a limitation of the stock ROM?
My concern is mostly for when I travel out of the country. I know from past experience I'll need to be able to select the proper APN to get the best connectivity, but I've also needed to select the correct APN locally sometimes like when my phone(s) freak out and only connect to the CDMA_0 APN so I'm stuck on 3G.
internetpilot said:
Anyone else running the G5S+ on Sprint? It's working fairly well for me other than a couple of IPv6/IPv4 connection issues. However, is it normal for Cellular network settings to not include any kind of APN settings/options? We have six different devices on our family Sprint account -- Nexus 6, Samsung Galaxy S5 Active, Samsung Galaxy S3, iPhone 7, iPhone 6+, and now the G5S+. All of the other devices have a way to edit the APN settings, even when running the stock, unrooted ROM. I'm waiting to root my G5S+ until after an official Oreo update. Is this a limitation of the stock ROM?
My concern is mostly for when I travel out of the country. I know from past experience I'll need to be able to select the proper APN to get the best connectivity, but I've also needed to select the correct APN locally sometimes like when my phone(s) freak out and only connect to the CDMA_0 APN so I'm stuck on 3G.
Click to expand...
Click to collapse
There should be, even on stock. Might be a problem with the sim - contact Sprint for help
Phazmos said:
There should be, even on stock. Might be a problem with the sim - contact Sprint for help
Click to expand...
Click to collapse
Oh, I already have contacted Sprint several times, and had the SIM switched out 3x now. This is a different type of Sprint SIM than I had in my Nexus 6. I think it's probably going to require root and modifying the build.prop or even a custom ROM, which I don't really want to do until the Oreo OTA comes out or at least a much more stable custom ROM than what we have now for this phone.
The Sprint network has gotten a little weird. First this new 3-in-one SIM, which seems to have locked-down APN settings, and then this phone also only has an IPv6 IP#, which is causing a couple problems with monitoring my IP security cameras at both my homes (neither of my ISP's are fully on IPv6 yet), but also even Google Weather and the Android Wear Play Store won't connect on my Asus ZenWatch 3 paired through this phone and only using mobile data. If I connect the phone to wifi (anywhere -- home, public, etc.), the IP cameras, Google Weather, and Wear Play Store all work fine. It's just bizarre that Sprint isn't running a dual stack IPv4/IPv6 network until everything is IPv6. Most things work fine on my phone -- regular Play Store, Netflix, all social media, and even TeamViewer and Plex, which both are hosted the same IPv4 networks that have the IPv4 security cameras . I guess it's because all these other services are running some kind of dual stack configuration at their end, but I'm very surprised that Google Weather and the Wear Play Store apparently is not.
I've yet to find anyone else who is using this phone on Sprint to confirm that they're encountering the same thing I am.
internetpilot said:
Oh, I already have contacted Sprint several times, and had the SIM switched out 3x now. This is a different type of Sprint SIM than I had in my Nexus 6. I think it's probably going to require root and modifying the build.prop or even a custom ROM, which I don't really want to do until the Oreo OTA comes out or at least a much more stable custom ROM than what we have now for this phone.
The Sprint network has gotten a little weird. First this new 3-in-one SIM, which seems to have locked-down APN settings, and then this phone also only has an IPv6 IP#, which is causing a couple problems with monitoring my IP security cameras at both my homes (neither of my ISP's are fully on IPv6 yet), but also even Google Weather and the Android Wear Play Store won't connect on my Asus ZenWatch 3 paired through this phone and only using mobile data. If I connect the phone to wifi (anywhere -- home, public, etc.), the IP cameras, Google Weather, and Wear Play Store all work fine. It's just bizarre that Sprint isn't running a dual stack IPv4/IPv6 network until everything is IPv6. Most things work fine on my phone -- regular Play Store, Netflix, all social media, and even TeamViewer and Plex, which both are hosted the same IPv4 networks that have the IPv4 security cameras . I guess it's because all these other services are running some kind of dual stack configuration at their end, but I'm very surprised that Google Weather and the Wear Play Store apparently is not.
I've yet to find anyone else who is using this phone on Sprint to confirm that they're encountering the same thing I am.
Click to expand...
Click to collapse
I'm glad I never used Sprint, mainly cuz I've heard of so many problems with them over the years, and where I am it's basically att or Verizon if ya want any kind of coverage (rural + mountains = shirty cell coverage). Did you get the phone from Sprint? I'm wondering if it's locked down for Sprint - last time I used a locked down device was about 6 years ago. I always thought apns were handled by the os, but if it's locked down, it could be handled by the sim. Now I'm curious - what would happen if you popped in a sim from one of those other devices that do work?
Unlock, root and roms - not many available right now (new devices always take a while - especially if uptake is slow), but what's out there now are pretty much stable enough for daily use. This device is supposed to get Oreo, but probably not till sometime next year (I'm not running it yet but only cuz the features I want aren't there yet). Ipv6 implementation - lol - I've worked with a few network engineers over the years and when the talk of ipv6 started up, they went crazy. Implementing it, even on a small scale isn't an easy thing, imagine on a nation wide, or world wide scale. It started about 5 years ago, and it'll probably take another 5+ before everything is compatible. Anyway, I ramble - good luck , I do hope it gets sorted out for ya!
Phazmos said:
I'm glad I never used Sprint, mainly cuz I've heard of so many problems with them over the years, and where I am it's basically att or Verizon if ya want any kind of coverage (rural + mountains = shirty cell coverage). Did you get the phone from Sprint? I'm wondering if it's locked down for Sprint - last time I used a locked down device was about 6 years ago. I always thought apns were handled by the os, but if it's locked down, it could be handled by the sim. Now I'm curious - what would happen if you popped in a sim from one of those other devices that do work?
Unlock, root and roms - not many available right now (new devices always take a while - especially if uptake is slow), but what's out there now are pretty much stable enough for daily use. This device is supposed to get Oreo, but probably not till sometime next year (I'm not running it yet but only cuz the features I want aren't there yet). Ipv6 implementation - lol - I've worked with a few network engineers over the years and when the talk of ipv6 started up, they went crazy. Implementing it, even on a small scale isn't an easy thing, imagine on a nation wide, or world wide scale. It started about 5 years ago, and it'll probably take another 5+ before everything is compatible. Anyway, I ramble - good luck , I do hope it gets sorted out for ya!
Click to expand...
Click to collapse
No, it's a carrier independent unlocked phone that I bought from BestBuy.com (because they offered the best price for the 64gb version through a Cyber Monday sale). Except for the iPhone (and maybe the newer Samsung models), Sprint phones don't have removable SIMs -- they're built-in to the phone making them a special Sprint-only phone. That's the way my Samsung Galaxy Note 2 was. After my Note 2, I bought an unlocked Google (Motorola) Nexus 6 and used a SIM to use it on Sprint (and had access to APN setting as soon as I activated the phone), but that SIM isn't compatible with the G5S+ even though they're both Motorola phones, have the same radios, etc. I'm pretty sure my current problem is the SIM, but I don't think it's unsolvable. I just think I'll need to root and mod or ROM the device to get access to those settings. I know this is one of Sprint's newest SIMs (they have like 22 different SIMs), so I'm sure this is just another attempt by Sprint to lock down unlocked carrier independent phones on their network to help reduce excessive roaming (on Verizon towers) which costs Sprint money.
I've been on Sprint for like 15 years. The only reason I stayed on them is because the others aren't really any better, and Sprint is the only one who truly offers unlimited everything (which is really good to have for a family of six). Starting like 3 years ago (when Sprint and Samsung abruptly abandoned the Samsung Galaxy Note 2 rather early), I refused to buy Sprint locked-down phones because they require to sign another 2 year contract commitment. Whereas right now if Sprint ticks me off (like they did a couple of years ago when they sent me a $500 bill for "free" international roaming), I can just immediately drop them and move on with no penalty and even take my phone with me.
This is the first Android phone I've owned that I haven't immediately rooted. I even rooted all my family's locked Sprint phones. There just isn't much support for this phone from 3rd-party devs (yet or maybe ever since it's just a "special edition" upgrade?), so I really want that OTA Oreo update in place before I root it. I came pretty close to immediately rooting this phone, but then decided not to when saw some people had problems getting it back to stock enough to take the OTAs from Moto. I actually like the Moto Android (along with a heavily themed Nova launcher) experience enough to not feel the overwhelming need for a custom ROM, so about the only thing I really want root for is to get a better camera app (preferably Google Camera), wifi tethering, and Titanium Backup. I'm even getting used to the stock Moto camera app, so I'm not really feeling the pressing need for the Google Camera as much. I wouldn't mind getting LineageOS 15 on here, but there isn't an official version and it doesn't seem very stable yet on any device. I tend to keep my phones for a while (three years for my Nexus 6 and Note 2), so I tend to outlast most 3rd-party dev ROM support, which is why I tend to just go with LineageOS (and before that CyanogenMod) which doesn't just vanish one day like individual dev ROMs do. We'll see what happens. Hopefully this phone will start seeing more developer activity. I was originally going to get the Moto G5+, which does have a lot more dev support, but considering how long I tend to keep phones, it didn't make sense not to buy the latest/greatest version.
I'm sure it will all eventually work out. Worst case scenario is that during a European vacation next Summer I won't be able to take full advantage of Sprint's free low speed international data roaming and texting, but even then I can always just grab a local PAYG SIM and use it.
internetpilot said:
No, it's a carrier independent unlocked phone that I bought from BestBuy.com (because they offered the best price for the 64gb version through a Cyber Monday sale). Except for the iPhone (and maybe the newer Samsung models), Sprint phones don't have removable SIMs -- they're built-in to the phone making them a special Sprint-only phone. That's the way my Samsung Galaxy Note 2 was. After my Note 2, I bought an unlocked Google (Motorola) Nexus 6 and used a SIM to use it on Sprint (and had access to APN setting as soon as I activated the phone), but that SIM isn't compatible with the G5S+ even though they're both Motorola phones, have the same radios, etc. I'm pretty sure my current problem is the SIM, but I don't think it's unsolvable. I just think I'll need to root and mod or ROM the device to get access to those settings. I know this is one of Sprint's newest SIMs (they have like 22 different SIMs), so I'm sure this is just another attempt by Sprint to lock down unlocked carrier independent phones on their network to help reduce excessive roaming (on Verizon towers) which costs Sprint money.
I've been on Sprint for like 15 years. The only reason I stayed on them is because the others aren't really any better, and Sprint is the only one who truly offers unlimited everything (which is really good to have for a family of six). Starting like 3 years ago (when Sprint and Samsung abruptly abandoned the Samsung Galaxy Note 2 rather early), I refused to buy Sprint locked-down phones because they require to sign another 2 year contract commitment. Whereas right now if Sprint ticks me off (like they did a couple of years ago when they sent me a $500 bill for "free" international roaming), I can just immediately drop them and move on with no penalty and even take my phone with me.
This is the first Android phone I've owned that I haven't immediately rooted. I even rooted all my family's locked Sprint phones. There just isn't much support for this phone from 3rd-party devs (yet or maybe ever since it's just a "special edition" upgrade?), so I really want that OTA Oreo update in place before I root it. I came pretty close to immediately rooting this phone, but then decided not to when saw some people had problems getting it back to stock enough to take the OTAs from Moto. I actually like the Moto Android (along with a heavily themed Nova launcher) experience enough to not feel the overwhelming need for a custom ROM, so about the only thing I really want root for is to get a better camera app (preferably Google Camera), wifi tethering, and Titanium Backup. I'm even getting used to the stock Moto camera app, so I'm not really feeling the pressing need for the Google Camera as much. I wouldn't mind getting LineageOS 15 on here, but there isn't an official version and it doesn't seem very stable yet on any device. I tend to keep my phones for a while (three years for my Nexus 6 and Note 2), so I tend to outlast most 3rd-party dev ROM support, which is why I tend to just go with LineageOS (and before that CyanogenMod) which doesn't just vanish one day like individual dev ROMs do. We'll see what happens. Hopefully this phone will start seeing more developer activity. I was originally going to get the Moto G5+, which does have a lot more dev support, but considering how long I tend to keep phones, it didn't make sense not to buy the latest/greatest version.
I'm sure it will all eventually work out. Worst case scenario is that during a European vacation next Summer I won't be able to take full advantage of Sprint's free low speed international data roaming and texting, but even then I can always just grab a local PAYG SIM and use it.
Click to expand...
Click to collapse
I've been following the few thread there are on this phone since I got it (about a month now), and others have had the same (no apn settings or can't change them) issue, but I just figured it was noob issues as I've always modified the apn and never had a problem, on stock or any of the roms available now, and I've tried them all. I'm an old tech guy (in age and computer experience - took my first computer class in 77) and at this point it's in my blood and I'm to old to change my ways! Still curious though - what do ya mean by the by sim wasn't compatible? Granted I'm on straight talk, but been using the same SIM - starting with the n5, then 6p, now g5s plus - I just cut it down to size when it went to the micro format. I to hope to see more work for this thing. Almost makes me want to get back into building again (been like 6+ years since I built a rom) but I just don't want to spend the time, which I don't really have anyway. I thought about the g5+, but I can't go back to a smaller screen. Yeah it wasn't much smaller, and has same cpu, and probably a better camera, but this pig will do. And with finger print actions and expanded desktop, screen is the same size as my 6p (which I was extremely happy with till the big cores shirt the bed - still running though). Wish the camera was as good, but if I really want to take a good picture, I have my nikon d5100 (hacked of course)!
Again, good luck, I'm sure you'll get it fingered out eventually!
Phazmos said:
I've been following the few thread there are on this phone since I got it (about a month now), and others have had the same (no apn settings or can't change them) issue, but I just figured it was noob issues as I've always modified the apn and never had a problem, on stock or any of the roms available now, and I've tried them all. I'm an old tech guy (in age and computer experience - took my first computer class in 77) and at this point it's in my blood and I'm to old to change my ways! Still curious though - what do ya mean by the by sim wasn't compatible? Granted I'm on straight talk, but been using the same SIM - starting with the n5, then 6p, now g5s plus - I just cut it down to size when it went to the micro format. I to hope to see more work for this thing. Almost makes me want to get back into building again (been like 6+ years since I built a rom) but I just don't want to spend the time, which I don't really have anyway. I thought about the g5+, but I can't go back to a smaller screen. Yeah it wasn't much smaller, and has same cpu, and probably a better camera, but this pig will do. And with finger print actions and expanded desktop, screen is the same size as my 6p (which I was extremely happy with till the big cores shirt the bed - still running though). Wish the camera was as good, but if I really want to take a good picture, I have my nikon d5100 (hacked of course)!
Again, good luck, I'm sure you'll get it fingered out eventually!
Click to expand...
Click to collapse
25-year career network engineer here myself -- I was on the internet since before it was called the internet (I guess "world wide web" didn't sound as kewl ). At this point in my life, I don't find technology as "fascinating" as I used to, and I pretty much just want it to work for me right out of the box. I know, I know...pipe dream. What's annoying for me is that I know this is a Sprint SIM/network issue (especially the IPv6 part), but to actually communicate with someone who even understands my questions is impossible because they're not working the help desk chat lines. Oh, well...I could go on and on with all kinds of funny stories, but the short of it is that I usually just fix my issues myself.
By the SIM being incompatible I mean just that. I took the SIM out of my Nexus 6 (which I loved, especially the camera -- broke my heart when it started randomly rebooting after 3 years of faithful service) and popped it in the G5S+ and it said "Incompatible SIM" and wouldn't register on the Sprint network. So, I took it to a corporate Sprint store (where I got the SIM for the Nexus 6) and thankfully a very knowledgeable employee was there, who said, "Yep, the G5S+ takes a specific model number of nano SIM." He popped that specific SIM in the G5S+, and it pretty much came right up on the Sprint network without an issue except for the APN thing and the IPv6 thing (which I discovered later). I have spoken with a mid-level Sprint network tech who told me that the whole IPv6 isn't my SIM as much as it's when I added that SIM and phone to the Sprint network. He said all new phones after a certain date are only getting IPv6. They supposedly were going to do something to my account that forced me back on IPv4, but it didn't actually work. They also said that it would only be for a few months anyway, because they're planning on converting everyone over very soon.
This phone is 1/2" smaller than my Nexus 6, but I actually like that. I feel like I'm on a tiny phone again...haha. Anyone I tell that to quickly points out that my G5S+ is a huge phone. I didn't think I'd like the fingerprint scanner, but I really do. I also thought I'd miss the dual front speakers on the Nexus 6, but I don't really even notice it since this speaker is so loud. I do miss the Nexus 6 camera which was superb, but I'm actually getting the hang of the G5S+ camera. I'm finding myself using the "professional" (manual) mode feature a lot, but I only change the ISO to 200 and leave everything else automatic and the pictures are vastly improved. If Moto would just provide an update that would allow post-processing to be turned off, it might actually be a very good camera. I too have a couple of really nice dedicate digital cameras that can take care of anything I really need in higher end photography or video. I've always only used my phone camera because I always have it with me. For tourist stuff, family events, etc., I always bring my real camera(s) anyway.
I've created my own custom ROMs and kernels before, but it's always just been modifying or adding to someone else's work, so I just used it myself and never released it here on XDA or anything. Depending on how things go for others, I might try doing my own LineageOS builds, but I'd much rather see an official build get going for this phone and just use that. But I said, I really don't mind that stock Moto ROM that much. It's pretty much vanilla Android, and once I root it a lot of the little customizations that go into most ROMs could probably be applied to the stock ROM in the form of a mod. We'll see.
Thanks again for the replies and commiserations!
internetpilot said:
25-year career network engineer here myself -- I was on the internet since before it was called the internet (I guess "world wide web" didn't sound as kewl ). At this point in my life, I don't find technology as "fascinating" as I used to, and I pretty much just want it to work for me right out of the box. I know, I know...pipe dream. What's annoying for me is that I know this is a Sprint SIM/network issue (especially the IPv6 part), but to actually communicate with someone who even understands my questions is impossible because they're not working the help desk chat lines. Oh, well...I could go on and on with all kinds of funny stories, but the short of it is that I usually just fix my issues myself.
By the SIM being incompatible I mean just that. I took the SIM out of my Nexus 6 (which I loved, especially the camera -- broke my heart when it started randomly rebooting after 3 years of faithful service) and popped it in the G5S+ and it said "Incompatible SIM" and wouldn't register on the Sprint network. So, I took it to a corporate Sprint store (where I got the SIM for the Nexus 6) and thankfully a very knowledgeable employee was there, who said, "Yep, the G5S+ takes a specific model number of nano SIM." He popped that specific SIM in the G5S+, and it pretty much came right up on the Sprint network without an issue except for the APN thing and the IPv6 thing (which I discovered later). I have spoken with a mid-level Sprint network tech who told me that the whole IPv6 isn't my SIM as much as it's when I added that SIM and phone to the Sprint network. He said all new phones after a certain date are only getting IPv6. They supposedly were going to do something to my account that forced me back on IPv4, but it didn't actually work. They also said that it would only be for a few months anyway, because they're planning on converting everyone over very soon.
This phone is 1/2" smaller than my Nexus 6, but I actually like that. I feel like I'm on a tiny phone again...haha. Anyone I tell that to quickly points out that my G5S+ is a huge phone. I didn't think I'd like the fingerprint scanner, but I really do. I also thought I'd miss the dual front speakers on the Nexus 6, but I don't really even notice it since this speaker is so loud. I do miss the Nexus 6 camera which was superb, but I'm actually getting the hang of the G5S+ camera. I'm finding myself using the "professional" (manual) mode feature a lot, but I only change the ISO to 200 and leave everything else automatic and the pictures are vastly improved. If Moto would just provide an update that would allow post-processing to be turned off, it might actually be a very good camera. I too have a couple of really nice dedicate digital cameras that can take care of anything I really need in higher end photography or video. I've always only used my phone camera because I always have it with me. For tourist stuff, family events, etc., I always bring my real camera(s) anyway.
I've created my own custom ROMs and kernels before, but it's always just been modifying or adding to someone else's work, so I just used it myself and never released it here on XDA or anything. Depending on how things go for others, I might try doing my own LineageOS builds, but I'd much rather see an official build get going for this phone and just use that. But I said, I really don't mind that stock Moto ROM that much. It's pretty much vanilla Android, and once I root it a lot of the little customizations that go into most ROMs could probably be applied to the stock ROM in the form of a mod. We'll see.
Thanks again for the replies and commiserations!
Click to expand...
Click to collapse
Lmfao - I know exactly how ya feel! I "retired" about 5 years ago, but people ask what did for a living and I say computers - then the questions start coming. I don't mind really, but I'm more thrilled by hitting a good golf shot than talking computers again. Now when they ask what I do I say , play golf! And leave it at that. Still, I just can't help myself when it comes to noobs - I still help folks out when I can, although my patience is much shorter than it used to be. It still amazes me how people do things without knowing their arse from a hole in the wall (xda has become pretty much a source of amusement for me nowadays). I did the same with roms, never went public with any - mostly cuz I didn't have the patience for stupid questions about things I've explained clearly. Some just don't appreciate the humor in giving a stupid answer to a stupid question! Oh well! Really most roms out there have more bloat than a stock rom - way too many "features" I'll never use - all I need is date in status bar (why this isn't a stock feature is beyond me), status bar brightness (auto brightness is always either to bright or to dim) and keyboard cursor control - anything more is useless and if I don't use it, I don't want it. I like things lean and mean. Really the main reason I root is to load a custom hosts file, I've been ad free for too long to start seeing them now. I thought about the n6 when it came out, but I only had the n5 for a year and wasn't ready to upgrade and 6 in did sound big (shamu was a perfect name for it). Of course I did jump on the 6p when it came out, and loved it, now I can't do anything smaller than 5.5 (that may be more a comment on eyes that are almost 60 yrs old though). At this stage, bigger is definitely better! And look at that, I ramble again (nothing on the golf channel so I run on). Anyway, pleasure chatting - and best of luck with the issue - sounds like it'll be short lived. And may be with the trouble - it is a decent device, plenty of power for most uses (only slowness I see is working big spreads in open office) and with my usage 10+ hrs of screen on time is easy to hit and have something like 20% battery left. A good deal for the $$ spent. Enjoy!
Okay, after looking into it more, here's what I think is happening/going to happen. I found a dial code that got me to a really good phone information screen (*#*#4636#*#*). I also found a site that stated country by country the compatibility of the US version of this phone when used internationally. It can pretty much get 4G in just about every country, so the Sprint international roaming feature should at least get me 2G, which is all they advertise anyway. Through the above dial code, I can choose from a lot longer list of Preferred Network Types, including GSM only, GSM/WCDMA, TD-SCDMA, etc. When I select these, it tries unsuccessfully to connect to that network type, and when it can't it just reverts back to LTE/CDMA (the Sprint default). I think that the APN option won't show up on the menu until I successfully connect to a network other than Sprint's. I'll find out next Summer as we're planning on going to Europe. At least I now know for sure that this phone can operated internationally just fine, so I can always go the PAYG SIM route. I looked into it on previous trips with my Nexus 6, and there are travel websites that tell you exactly the best SIM service to get for each country.
Otherwise, like I said, it seems to be working fine on Sprint. On my Nexus 6 I would have problems with it switching APNs on me from the Sprint LTE APN to the one of the 3G CDMA APNs so I'd lose 4G LTE service until I switched it back. I haven't had that problem with my G5S+ so far, so I haven't "needed" the APN option in the menus yet. Hopefully I won't. I'm about to go from Virginia to Florida for the Christmas holidays, so it will be interesting to see how things work in a different location. Sprint service at my Florida house isn't exactly stellar (none of the providers are), so it should be a good test of this phone and the lack of access to APN settings.
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
internetpilot said:
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
Click to expand...
Click to collapse
Ok yes I'm on Sprint. So I can get to those apn settings but I can't add an apn.. exactly how do you do that.. Yes I can edit the only existing one just can't add any.
edit APN settings for IPV4
also posted here: https://forum.xda-developers.com/mo...ing-ipv4-address-sprint-t3747256#post76243857
First please forgive this post if it is not helpful, I didn't see a solution and came up with something that worked for me, so hope it will help others.
Problem: On my Moto XT1806 GS5+ I was getting no IPV4 connectivity only IPV6 (tested with app: Ping & Net by Ulf Dittmer from the play store).
The main issue this caused was that I couldn't view my security cameras via Sprint's network., It would only show cameras on my home WIFI.
To verify I used Ping & Net to try to ping google.com. The app gives you the option to use IPV4 or IPV6, as you can guess IPV6 succeeded and IPV4 gave no results at all.
With some guesswork I did the following to fix this:
Solution:
open dialer and typed *#*#DATA#*#* or *#*#3282#*#* selected apn settings then internet.
at the top right tap the 3 dots and select edit this prompted me to enter a passcode which after several guesses ended up being 6 zeros "000000". (maybe this is in the instructions somewhere? Don't know didn't look, kinda figured it would be posted already if it was).
then I was able to change the APN NI from x.ispsn to n.ispsn.
Waited a few seconds, turned on airplane mode and then turned it back off and then I was on 3G with IPV4. It would be even better if it was LTE with IPV4, I will continue to experiment, or maybe someone can step in and save me the trouble. maybe cinet.spcs?
Anyway it works for now as a workaround and I can look at my security cameras away from home again, hooray.
gravityecho said:
also posted here: https://forum.xda-developers.com/mo...ing-ipv4-address-sprint-t3747256#post76243857
First please forgive this post if it is not helpful, I didn't see a solution and came up with something that worked for me, so hope it will help others.
Problem: On my Moto XT1806 GS5+ I was getting no IPV4 connectivity only IPV6 (tested with app: Ping & Net by Ulf Dittmer from the play store).
The main issue this caused was that I couldn't view my security cameras via Sprint's network., It would only show cameras on my home WIFI.
To verify I used Ping & Net to try to ping google.com. The app gives you the option to use IPV4 or IPV6, as you can guess IPV6 succeeded and IPV4 gave no results at all.
With some guesswork I did the following to fix this:
Solution:
open dialer and typed *#*#DATA#*#* or *#*#3282#*#* selected apn settings then internet.
at the top right tap the 3 dots and select edit this prompted me to enter a passcode which after several guesses ended up being 6 zeros "000000". (maybe this is in the instructions somewhere? Don't know didn't look, kinda figured it would be posted already if it was).
then I was able to change the APN NI from x.ispsn to n.ispsn.
Waited a few seconds, turned on airplane mode and then turned it back off and then I was on 3G with IPV4. It would be even better if it was LTE with IPV4, I will continue to experiment, or maybe someone can step in and save me the trouble. maybe cinet.spcs?
Anyway it works for now as a workaround and I can look at my security cameras away from home again, hooray.
Click to expand...
Click to collapse
Just found easier/better way to get/test IPV4: dial *#*#4636#*#* select phone info, from this screen you can run ping test to see if IPV6 and/or IPV4 is working. In my case, changing network type from "LTE/CDMA auto (PRL)" to "CDMA only" gave me a pass ping on IPV4.
This seems like a much easier/faster/better method than previous post and is now my preferred workaround method.
gravityecho said:
Just found easier/better way to get/test IPV4: dial *#*#4636#*#* select phone info, from this screen you can run ping test to see if IPV6 and/or IPV4 is working. In my case, changing network type from "LTE/CDMA auto (PRL)" to "CDMA only" gave me a pass ping on IPV4.
This seems like a much easier/faster/better method than previous post and is now my preferred workaround method.
Click to expand...
Click to collapse
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
internetpilot said:
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
Click to expand...
Click to collapse
Yeah after talking to support at my ISP (Cox who doesn't support IPv6 yet at least in my area), Sprint (who would love to sell me another phone), Motorola (who suggested I reset app preferences and restart) and Best buy (who didn't have a clue but again would love to sell me another phone), yesterday I had enough and returned it. It's staggering how many people in tech support fields have no idea what IPv4, IPv6, and APNs are. One support person at sprint thought IPv4 meant Iphone 4... Back to my trusty Note 4 with it's emmc problem and cinet.spcs.
internetpilot said:
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
Click to expand...
Click to collapse
I just recently bought a G5S Plus to replace my G5 Plus, because the screen on my G5 is cracked and I was going to fix the screen, but then I've found that the Micro USB port on the bottom is also growing "lose" (I HATE!!!! Micro USB because they always wear out on my phones).
Anyway, I went to "activate" my new G5S+ on the Sprint web page and it just said sorry they can't help w/that, I have to "Speak to someone for assistance" (but they didn't show me what phone number to call).
Glad to see the phone will actually work on Sprint! (Since I already bought it, it would be a big deal for me if it did not!).
I have not rooted mine yet, but plan to soon. I am just not sure what ROM to use yet because it seems like these days there is no such thing as a custom ROM without problems. I sure miss the days of my Samsung Galaxy S3 when most ROMs I tried seemed to be basically flawless and better than Stock, or, at least as good, in every way.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
internetpilot said:
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
Click to expand...
Click to collapse
Damn, wow, that really sucks. I have this phone, it's too late to return it, and I've got about 6 months left of my "unlimited everything" from sprint for approximately $3 per month.
critofur said:
I just recently bought a G5S Plus to replace my G5 Plus, because the screen on my G5 is cracked and I was going to fix the screen, but then I've found that the Micro USB port on the bottom is also growing "lose" (I HATE!!!! Micro USB because they always wear out on my phones).
Anyway, I went to "activate" my new G5S+ on the Sprint web page and it just said sorry they can't help w/that, I have to "Speak to someone for assistance" (but they didn't show me what phone number to call).
Glad to see the phone will actually work on Sprint! (Since I already bought it, it would be a big deal for me if it did not!).
I have not rooted mine yet, but plan to soon. I am just not sure what ROM to use yet because it seems like these days there is no such thing as a custom ROM without problems. I sure miss the days of my Samsung Galaxy S3 when most ROMs I tried seemed to be basically flawless and better than Stock, or, at least as good, in every way.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
Damn, wow, that really sucks. I have this phone, it's too late to return it, and I've got about 6 months left of my "unlimited everything" from sprint for approximately $3 per month.
Click to expand...
Click to collapse
Yep, welcome to my world! I think we're the only two people on the Moto G5S Plus on Sprint here! I was a little surprised when the SIM from my Motorola Nexus 6 didn't work in the Moto G5S Plus, but that's probably the reason you have to talk to someone or go to a Sprint store to activate it because this phone does require a rather specific SIM that's different from the previous Moto G and E models. At least Sprint finally solved the IPv6 issues that were going on when I first got this phone. That was pretty bad. It got better when my home internet providers (Comcast and Verizon at two different houses) finally upgraded to IPv6, but Sprint really shouldn't have pulled the trigger on implementing IPv6 so early. To this day only like 25% of the entire internet is on IPv6 and in the world only like 50 countries have more than 5% of IPv6 implemented.
I've literally tried every ROM posted here and even the unofficial versions of very popular ROMs (that have always worked for me on my Android phones with Sprint) like Dirty Unicorns, Resurrection Remix, LineageOS, etc., all do the same thing. They all seem to be using the same proprietary blobs or base or whatever (I'm not a developer), and they just simply don't work (or are at least VERY sketchy) on Sprint. I've been rooting/ROMing Android since my first phone almost a decade ago (HTC EVO 4G), and never had these problems on Sprint before this phone. My immediate previous phone was also a Motorola (Google Nexus 6), and I never had any problem with Sprint and custom ROMs on that phone.
I actually just recently flashed everything back to unrooted stock Nougat, took the Oreo update and all the security updates, and didn't even bother to re-root it. Sprint put a free 50GB/month wifi hotpot on every phone on my account, and the Camera2 API is activated in the stock Oreo ROM, so other than flashing a custom ROM, those were my two main reasons for rooting and they're no longer needed. So, I'm currently happily running stock unrooted Oreo with Nova Launcher.

SM-G973U VoLTE

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).

Categories

Resources