Database Users

Question about cross-carrier compatibility

Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.

YamiYaiba said:
Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.
Click to expand...
Click to collapse
I would defer to my boss or VZ corporate lest I get fired for doing the "wrong thing", which I learned on an internet forum!

UNBELIEVABLE
Sent from my SM-G900V using XDA Free mobile app

YamiYaiba said:
Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.
Click to expand...
Click to collapse
No offense, I'm actually trying to do the opposite and move my Verizon S5 and S3 to T-Mobile. (Verizon phone reps, through six separate phone calls, gave me six different stories of how to unlock my phone. I'm experiencing hiccups as I go - T-Mobile gave me some misinformation as well.)
They were able to change a lot of settings for their network, there are still SMS issues and other random odd issues. Maybe that's the nature of it?

I haven't looked into this in over a year, but I was under the impression that Verizon operates on an IMEI white list, i.e. ONLY Verizon branded phones are allowed on the network. When a user attempts to activate a phone on the network, it's IMEI is checked against the list of IMEIs for every phone Verizon has sold. If it's IMEI is not on that list because it's a non-carrier branded phone or it's another carrier's version of the phone it will not be allowed on the network regardless of hardware compatibility.
From what I recall, this was also the reason that Nexus 7 LTE buyers were screwed by Verizon. Verizon was advertised as supporting the tablet because legally they had to due to the open access provision they agreed to when they purchased their LTE spectrum. Up to that point Verizon had operated with a white list as I described above. They were able to get away with this despite the open access provision because they run voice and text over the older 2G and 3G networks on which they have not agreed to open access. When the tablet came out, for months Verizon had no system in place to activate it because the IMEIs were not on the white list. Users were able to successfully connect to the network with a SIM activated in another tablet proving that it was not a hardware issue.
Has this changed in the last year? If so that great news!
---------- Post added at 12:25 PM ---------- Previous post was at 11:58 AM ----------
I just Googled it, and based on information from November when the Nexus 6 came out, Verizon still operates on a white list, but it's only for activating NEW LINES. Verizon will not allow you to activate a new line with a non-Verizon branded phone, however, once the SIM has been activated, if it is placed in a non-white listed phone, that phone will be allowed on the network.
Some people suggest that you can take the IMEI of a floor model at the Verizon store and enter that when you order a SIM CARD, and that will allow for activation. I cannot personally verify this as I'm not a Verizon customer, and I'm not sure if the SIM activation process requires an actual phone with a white listed IMEI.
---------- Post added at 12:51 PM ---------- Previous post was at 12:25 PM ----------
Also OP, have you verified that the handsets with SMS problems support all of Verizon's 2G and 3G network frequencies? From what I recall, Verizon still runs voice and SMS over its legacy 2G/3G networks. I'm not sure if they've implemented Volte yet, but it's likely that older handsets and even some newer ones don't support it, especially if they don't have a Verizon ROM. It's possible that a handset could support only Verizon's LTE frequencies or support everything except it's 3G frequencies for example. If it supports only the LTE frequencies, data could work while voice and SMS don't. If voice and SMS are run over different frequencies it's possible that only one of the two will work.
Information on supported frequencies can be tough to find for phones sold in the US. The information is readily available for the same phones sold anywhere else in the world. The most plausible explanation is that this is because the US carriers insist upon it. They've been forced to start unlocking phones that in the past they've been able to permanently lock to their own networks for domestic use. To combat the emergence of a free marketplace where customers are free to move to a carrier offering a better deal, the carriers have started specifying that their carrier branded versions of the phone be shipped with firmware (possibly also hardware variations) that does not support the frequencies of other US carriers. That way, the phone is "unlocked," but it still won't work on other US networks, so they've managed to sidestep the legislation and continue screwing over consumers.
If the supported frequencies aren't listed on the manufacturer website, you can find them in FCC testing documents.
If customers do have a problem where voice or SMS doesn't work because the frequency isn't supported, they could use a Google voice number for calls and SMS over the data network using the Hangouts app. It works great for me. Your employer definitely would not approve of this suggestion though, since it compromises the way they've artificially limited their technology to force consumers to pay more. All calls and texts to/from a Google voice number are totally free when you're on a Wifi network, and the number is device agnostic, so there's no barrier at all to switching phones or carriers. Verizon wants to use your phone number to make switching as inconvenient as possible, so they don't want you using a cloud based phone number.

No VOLTE and no WiFi calling T-Mobile, what gives?

I'm gonna make a post here since NOTHING seems to be working. I'm a T-Mobile customer. Yesterday, I purchased a great condition nexus 6P from someone because my LG G5 is cracked and I was getting tired of it anyway so I opted to just buy a nexus instead of using my insurance on that phone. Everything is all good except for one major issue. VOLTE and WiFi calling just refuse to work with my sim in the Nexus.
I've called T-Mobile twice. I've factory reset from back up and reset settings twice. I've hard reset from stock recovery once. I've wiped network settings and restored default apns. I've manually changed the apns from what I see on Google, reddit and here. I've copied my apns from my LG G5 where VOLTE and wifi calling work perfectly fine. I've cleared cache. I've cleared the cache of the project fi and hangouts apps just in case there's something left over from the previous owner. I've gone into the *#*#4636 menu and tried a bunch of different stuff several times but no matter what I absolutely can not get wifi calling or VOLTE to work with TMobile on my nexus 6P. LTE it's self works perfectly fine for data.
Yes, all settings for wifi calling and enhanced LTE calling and VOLTE are turned on lol. I've tried the trick where you toggle wifi preferred on and off and restart the phone. Nothing happens. I don't even get a wifi calling reg error. It never shows as active in the data toggle in the quick settings are nor the status bar or dialer. It just isn't active. Same for VOLTE. I AM getting band 12. I can see it in the LTE discovery app. VOLTE just isn't working though. Whenever I make a call I can see LTE switching off and it switches to HSPA therefore making calls really difficult in my shoddy signal area at my house which is why I really need it to work.
I'm fairly certain I can root and install a ROM which will fix these problems but I don't own a PC. . I thought MAYBE the previous owner had previously had the phone rooted and tinkered with something somewhere that may have messed something up but that doesn't appear to be the case. Bootloader is locked and recovery is stock.
Can anybody help and tell me what in the world is going on here? I don't want to have to sell this nexus and revert back to my cracked screen G5. I would just switch carriers but I still owe money on the G5 so I was just gonna ride it out til I payed it off.
O and one last thing, after scowling google and forums for hours on end yesterday and today I did see one post mentioning something about this stuff being related to IMS provisioning and settings which are tied to a phones IMEI on T-Mobile and not the sim card and how that person simply called T-Mobile and got a hold of wifi calling technical support who was clueless but created a ticket for him and within 72 hours the issue was resolved. OK well I did the same exact thing and they refuse to create a ticket for me because it's not a T-Mobile phone and because according to them they are not allowed to create a ticket because wifi calling works fine in my G5 and therefore it's the phone and not them or their network lol. What a crock. I'm willing to bet if I put the sim in another unlocked phone with 7.1.1 and wifi calling fully available that it isn't going to work either. There's some sort of communication error going on between the sim being in this phone and their network it appears.
Check these screenshots out. T-Mobile is clueless
http://imgur.com/5MuO34s
http://imgur.com/XVd8CdA
http://imgur.com/uUGN3ae
http://imgur.com/cfYxfqh

I can only suggest;
1) Find a PC and re-flash the latest factory images from Google. Both "fastboot flashing unlock" and "fastboot flashing lock" will wipe all data, so backup first. Also confirm it fully boots correctly after flashing before you re-lock the bootloader.
2) Get a new 3-in-1 SIMM from T-Mobile. You can use their web site to switch cards and give it 24 hours to be fully provisioned.
3) Confirm your E911 address is correct on T-Mobile's site and wait 24 hours after any changes for Wi-Fi calling to actually start working.

I HAVE THE SAME EXACT PROBLEM AS YOU POSTED!!! GONE THRU THE SAME PAIN. LOL I'll attempt the ticket thing to see if I get anywhere. Did you ever get it resolved?
EDIT:
My theory is that since the phone was used in Project FI, they specifically turn off this feature in the back end for the specific phones, by Imei or something since project FI uses T-Mobile as well.
EDIT 2:
they wont' create a ticket for me either. I guess I will just have to ride it out.
EDIT 3: I FIXED IT!! NEXUS 6P VOLTE AND WI-FI CALLING FIX T-MOBILE
I flashed back to android 6.0 Build#: MMB29N (I used the Nexus ToolKit 2.1.9: google it. BTW, your phone will be wiped, so backup first) VOLTE just started working with this version of android 6.0. Then I upgraded using the OTAs and now i'm on 7.1.1 build#: N4F260 with VOLTE and Wifi calling working as it should! I hope this helps someone out there!

For what it's worth, reverting to the build you mentioned fixed it for me on my two Nexus phones coming from Project Fi to T-Mobile as well! Thanks for the help!

You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.

banancanard said:
You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.
Click to expand...
Click to collapse
wish I had seen this sooner. cheers!

Had the exact same issue and this fix worked for me. Wasted a couple of hours with T-mobile (they were actually very helpful and debugged everything on their end to confirm the provisioning was good) and then 2+ hours with Google support. Actually had already filed for a device replacement which I canceled after finding this post.

I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?

k2kevink2 said:
I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?
Click to expand...
Click to collapse
Flashing the radio -sadly- requires an unlocked bootloader.

Did you resolve your problem?
In android 7.1.2 did you notice in Set preferred network type is set at " LTE/GSM/CDMA auto (PRL) "? 7.1.2 has been giving me issues with sms/mms. I noticed Android 6.0 has this set to correct T-mobile bands.

All works for me in 7.1.2. Make sure you don't download the Verizon version of the stock ROM. That was my issue why I couldn't have volte and Wi-Fi calling

three verizon nougat questions

I am currently on 935U, Marshmallow 6.01 PL4 (phone is a verizon Edge s7), unrooted.
1) I have read that the samsung dialer is no longer on Nougat , nor is the Samsung caller id?
Can someone verify if this is true? From reading further, I am not sure if it is the aesthetics that have changed or the actual dialer. My favorite feature of the edge 7 is the suspected spam id and block that comes up as a call comes in and also, sthe small window that comes up at the top of the phone to answer a call when you are in another app. Can anyone who has taken verizon nougat tell me if these features are no longer available?
2) I have read that tethering is not available on nougat without tweaking. Is this the same as mobile hotspot? I currently use mobile hotspot for my tablet when I am traveling and wifi signal is poor. I connect to the mobile hotspot using bluetooth. Can someone verify whether or not this option is available on Verizon Nougat without tweaking?
3) Lastly, my phone has lagged up greatly lately, I am considering flashing back to verizon software and taking nougat. If I am unhappy, will I be able to go back to 935 Marshmallow (currently on PL4) or is reverting back to Marshmallow not a possibility.
thanks in advance!

I'm not sure if it's the dialer either, bit give hiya a trt. It's by whitepaper and blocks spam really well, plus you can submit numbers as well for blocking.

tmord1 said:
I am currently on 935U, Marshmallow 6.01 PL4 (phone is a verizon Edge s7), unrooted.
1) I have read that the samsung dialer is no longer on Nougat , nor is the Samsung caller id?
Can someone verify if this is true? From reading further, I am not sure if it is the aesthetics that have changed or the actual dialer. My favorite feature of the edge 7 is the suspected spam id and block that comes up as a call comes in and also, sthe small window that comes up at the top of the phone to answer a call when you are in another app. Can anyone who has taken verizon nougat tell me if these features are no longer available?
Click to expand...
Click to collapse
This has never been available on Verizon firmware. Not even on 6.0. Verizon ripped the feature out to force you to buy "Verizon Caller ID" instead.
2) I have read that tethering is not available on nougat without tweaking. Is this the same as mobile hotspot? I currently use mobile hotspot for my tablet when I am traveling and wifi signal is poor. I connect to the mobile hotspot using bluetooth. Can someone verify whether or not this option is available on Verizon Nougat without tweaking?
Click to expand...
Click to collapse
"Mobile Hotspot" and "tethering" are the exact same thing. Most people who say "tethering" are referring to PDANet or whatever, because they're on grandfathered UDPs and refuse to switch to new plans. I have Wifi, Bluetooth and USB available as options for sharing my phone's LTE connection to a computer or tablet - I can even plug my phone into my router and have my router use it as the modem for my entire home network.
3) Lastly, my phone has lagged up greatly lately, I am considering flashing back to verizon software and taking nougat. If I am unhappy, will I be able to go back to 935 Marshmallow (currently on PL4) or is reverting back to Marshmallow not a possibility.
thanks in advance!
Click to expand...
Click to collapse
Generally, "lagging" is due to rogue apps and/or a corrupt cache. I would look at any apps that have suspicious permissions (why would a flashlight app need to access your contacts, for example) and dump them, and clear the cache.
As of right now, I'm running Verizon's 7.0 side by side with U 6.0.1 on two different Edges. 7.0 is beautiful and fast, but Verizon changes too much and removes too many features. If you only have one device, I would stick with the U FW and wait till next month for the U 7.0 update. My two cents.

@raduque Really appreciate the detailed answer!

You're welcome tmord1!

Moto X Pure Secret Codes

I post here directed how to get some info about our phones by dialing *#*#4636#*#*. Being curious, i found this link to do more:
http://mobilespecs.net/phone/codes/Motorola/Motorola_Moto_X_Pure_Edition_2015.html
CAUTION!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Some seem pretty dangerous so use at your own risk. At worst, I guess they could brick your phone but I am reasonably sure will not launch any nukes.
Enjoy, or not.
Specifically, I read about turning on WiFi Calling which I thought was not possible on my VZW MXP. A Magisk module, "VoEnabler", says it will turn it on and seems to do so. Causing concern was that VoLTE settings were now gone. The code at the top presents a menu of info one of which showed VoLTE was still provisioned. Makes me think Magisk module, "VoEnabler", is dual purpose. Turns on both VoLTE and WiFi Calling?

schneid said:
I post here directed how to get some info about our phones by dialing *#*#4636#*#*. Being curious, i found this link to do more:
http://mobilespecs.net/phone/codes/Motorola/Motorola_Moto_X_Pure_Edition_2015.html
CAUTION!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Some seem pretty dangerous so use at your own risk. At worst, I guess they could brick your phone but I am reasonably sure will not launch any nukes.
Enjoy, or not.
Specifically, I read about turning on WiFi Calling which I thought was not possible on my VZW MXP. A Magisk module, "VoEnabler", says it will turn it on and seems to do so. Causing concern was that VoLTE settings were now gone. The code at the top presents a menu of info one of which showed VoLTE was still provisioned. Makes me think Magisk module, "VoEnabler", is dual purpose. Turns on both VoLTE and WiFi Calling?
Click to expand...
Click to collapse
Not really a secret and many listed are extremely dated (early 2000's) generic codes or carrier specific... if you went down the list I bet you would find 75% of them don't do anything. There are some apps in the play store that do similar things but from a menu (it invokes the system application the code is used for), one that comes to mind is called Hidden Menus but I am sure there are others.

LS997 on US99610p - no LTE or internet

I've researched and done as much homework as I can but I can't seem to find the solution, so I'm starting this thread in the hope that someone can point me in the right direction. I've had an LS997 on Sprint since it launched but recently broke the screen a second time. After getting a couple bum screens off ebay, I decided to just purchase a new V20. Found one on ebay that was an LS997 unlocked. Figured why not, hopefully it is rootable and I can do some stuff with it. Got the phone, swapped my SIM, chatted with Sprint customer support, and got the phone to receive calls and texts. However, it wasn't getting LTE coverage like my old V20 and could not connect to the internet via mobile network (WiFi works fine).
The new phone is an LS997 (FCC ID: ZNFLS997) with software US99610p, build number NRD90M, Android security patch April 1, 2018. I am guessing that part of the trouble here could be that I am unable to activate fully with Sprint since I am not on a Sprint ROM (no option to update PRL, profile). Are there any working Sprint-based ROMs out there that I haven't stumbled upon?
I'm also wondering if the missing Sprint bands on the US996 firmware is giving me issue. SignalCheck Pro shows my old phone bouncing between bands 25 and 26 at my house, and obviously the US996 firmware doesn't have band 26. With the new phone being LS997 hardware, is there any way for me to gain access to those bands (by flashing a modem, etc)?
Any help would be greatly appreciated!

Rooted LS997 owner here. Yes, you have to be on a Sprint ROM to complete activation. Without completing that step, I don't think you can get everything to fully work on Sprint's network. The cross-flashed US996 firmware is useful for GSM networks around the world but not for Sprint or its MVNOs. Since Sprint does not provide firmware (KDZ) files, you'll have to go through the rooting process (check this guide) and then install a Sprint ROM (I recommend ClassicRom) at the end. If I remember correctly, there is a step during the rooting process where you flash some Sprint firmware that should take care of the modem part.

felixdacat76 said:
I've researched and done as much homework as I can but I can't seem to find the solution, so I'm starting this thread in the hope that someone can point me in the right direction. I've had an LS997 on Sprint since it launched but recently broke the screen a second time. After getting a couple bum screens off ebay, I decided to just purchase a new V20. Found one on ebay that was an LS997 unlocked. Figured why not, hopefully it is rootable and I can do some stuff with it. Got the phone, swapped my SIM, chatted with Sprint customer support, and got the phone to receive calls and texts. However, it wasn't getting LTE coverage like my old V20 and could not connect to the internet via mobile network (WiFi works fine).
The new phone is an LS997 (FCC ID: ZNFLS997) with software US99610p, build number NRD90M, Android security patch April 1, 2018. I am guessing that part of the trouble here could be that I am unable to activate fully with Sprint since I am not on a Sprint ROM (no option to update PRL, profile). Are there any working Sprint-based ROMs out there that I haven't stumbled upon?
I'm also wondering if the missing Sprint bands on the US996 firmware is giving me issue. SignalCheck Pro shows my old phone bouncing between bands 25 and 26 at my house, and obviously the US996 firmware doesn't have band 26. With the new phone being LS997 hardware, is there any way for me to gain access to those bands (by flashing a modem, etc)?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Seems you got lucky yourself on finding a rootable. I just got my new rootable ls997 last night. Have yet to run Dirty Santa to full root again. Very rare phone. I agree with C D here tho. Classic ROM is made specifically for ls997 and is the least buggy stock based custom ROM and is best for full activation. Also MK2000 BTTF Kernel is solid just in case.

I appreciate the responses! Looks like I'll be giving the Classic ROM a shot this week.

Good luck. And I second the recommendation for the mk2000 BTTF kernel (you can find it here).
One of the things this kernel does is get rid of LG's root checker called RCTD, which seems to log random things on rooted phones. You don't hear much about it any more because all the more recent ROMs have automatically gotten rid of it through their own kernel settings. I don't know a whole lot about RCTD itself, but if curious, there's some info here.
Also, the kernel allows you to change the KCAL screen color settings via a kernel manager like this one to help prevent any temporary screen retention (which you may already be familiar with). There are also some XDA threads where people posted different KCAL values that worked for them:
https://forum.xda-developers.com/v20/themes/post-kcal-values-t3865442