Database Users

[Guide] How to switch from AT&T to T-Mobile and keep your SM-N900A fully functional

[Guide] How to switch from AT&T to T-Mobile and keep your SM-N900A fully functional
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
Background
I always hated AT&T. When I got my first US cell phone in 1998, AT&T was a dominant force and Cingular was the underdog that provided better service. So for years I went out of my way to keep it Cingular through all of my relocations and phone number changes. Then AT&T bought Cingular and I was forced to become an AT&T subscriber. Then the iphone came along on the AT&T network, with the unlimited internet plan, which sealed my fate with this carrier for years.
At some point AT&T stopped offering the unlimited plan and I was one of the lucky ones who had their iphone plans grandfathered in. That prevented me for a long time from switching, but it became increasingly clear that AT&T has no intention of letting me use my plan as intended. All the signs were there: from threatening text messages every time I tried to tether my phone, to insulting slow-downs of data transfer after 2-5G of usage. At some point one gets tired of feeling like a criminal who is constantly trying to trick the carrier to squeeze a little more service here and there.
The last straw was when they made it very clear that they will not allow me to use a tablet as a phone, even if it has phone capabilities, even if I let go of my unlimited data plan! Their solution? buy a new data-plan only for your tablet. I am done with this $#(^. T-mobile had me at hello. All it takes is to notice the choice of music they play for you when you are on hold with the customer service: ATT: elevator music, T-mobile: Miley Cyrus.
So, here is what I did to make the switch and keep my note 3 issued by AT&T to use on T-mobile network.
Why?
If your phone is unlocked you can certainly pop the new sim card in and it will latch on to the T-mobile network. However you will be missing all the goodies that come with a T-mobile issued phone. Hence my journey to T-mobilize my SM-900A. A T-mobile Note 3 has an unlocked bootloader. I cannot have that transferred to an AT&T phone. But there are other good things that can be ported over. For example T-mobile's WiFi calling is implemented at the OS level and you cannot just copy over an APK to make it work. So if you follow this guide you will be able to turn your phone on and boot it up to (almost) exactly what a SM-N900T looks and behaves like.
Requirements:
1- Your phone should be on Jelly bean 4.3. Mine was on N900AUCUBNB4 but lower versions will work too. I have no intention of upgrading my phone to Kitkat anytime soon because I simply do not see the advantage. However, an experienced developer should be able to modify this process for Kitkat.
2- Your phone should be rooted.
3- You will need about 5G of empty space to install the T-mobile ROM.
4- Read the instructions below once before you start anything. If any word or phrase does not make sense to you STOP, google, ask questions, make sure you understand it, then continue.
Instructions:
1- Always backup your important stuff before doing a thing like this to your phone.
2- Root your phone if it already isn't. Your options that won't trip knox are Kingo and Towelroot. I recommend the latter.
3- dwitherell has done a great job of preparing a Jelly Bean T-mobile Rom for porting to AT&T. Download TweakedN3v2.0.12614 from http://forum.xda-developers.com/showthread.php?t=2625946
4- This ROM is pre-rooted but contains a few things that should be removed or tweaked for our purpose. Unzip it somewhere.
5- Delete vrtheme directory and bootcolx.img and bootstock.img
6- Replace defaults\install.prop with the file attached below.
7- Replace META-INF\com\google\android\updater-script with the file attached below.
8- Re-zip the whole thing again and call it N3-Tmobile.zip (or whatever you want)
9- Copy that to your sdcard. It may also be a good idea to copy a file manager apk like "File Manager HD" on your sdcard as well so you can later install it when the T-mobile Rom is in place.
10- Install Note 3 AT&T Safestrap 3.71 for Jelly Bean on your phone. It can be found at: http://forum.xda-developers.com/showthread.php?t=2572978
11- Boot into Safestrap recovery and create a Rom slot. Call it T-mobile or whatever you like. Activate it.
12- From the Safestrap main menu, install the N3-Tmobile.zip that you created in step 8 into the T-mobile slot. Be careful not to mess up your Stock Rom slot. The installation may take 3 to 10 minutes. If it takes longer, reboot the phone, wipe this Rom slot and try again.
13- When it is done, go to Safestrap main menu -> wipe -> advanced wipe -> select ONLY Dalvic, data, and cache, and the hit the wipe button.
14- Turn off the phone. Take out your AT&T sim card out, DON'T put your T-Mobile sim card in yet. Turn the phone on and reboot to the T-mobile Rom. Don't enable Wifi in the initial setup.
15- Now your T-mobile Rom is up and running but you don't have internet or cellular connections.
16- In your /system/app directory rename the following to [file_name].apk.bac (this is where the second part of step 9 becomes useful):
FotaClient.apk
FWUpgrade.apk
LocalFOTA.apk
SPPPushClient_Dev.apk
SyncmlDM.apk
16- Turn your phone off, put the T-mobile sim in it, turn on and enjoy.
If you want to swap the sim card back to AT&T, all it takes is to reboot to your stock ROM. Everything will be still there as you left them.

does it work?

Screen shots
Here is how well it has worked for me so far. I'm in Sweden now and their free sms abroad and unlimited Internet has so far worked as promised (although at data rates close to 100kb/s only which is expected. In the first screenshot I'm turning wifi off and as you can see the phone registers on to the local carrier. In the next screenshot I turned wifi calling on which allowed me to call back to the US for free. There was a half second audio delay but the quality was very good. Finally I attached my home screen shot that shows the T mobile apps that you get after this installation.
So far everything has been working great in the US and in Europe for me but please post your experience here if this has worked for you too.

Just to make sure we are on the same page, you had an ATT N3 and did this guide to get the TMO network. Is your baseband and broadband tmobile? That is what I am looking at. The ATT N3 works but I want the TMO Broadband / modems. Can you take a pic on the broadband page please. Does this chicken stract make sence?

chargedbird said:
Just to make sure we are on the same page, you had an ATT N3 and did this guide to get the TMO network. Is your baseband and broadband tmobile? That is what I am looking at. The ATT N3 works but I want the TMO Broadband / modems. Can you take a pic on the broadband page please. Does this chicken stract make sence?
Click to expand...
Click to collapse
Yes, i have an att n3 and i want it to work on t mobile network. The only thing this method flashes onto your phone is a /system partition. In fact that is all that you can do with safestrap. In one of the steps I am instructing you to remove the baseband from the zip so when you are done your baseband is still ATT.
I'm not sure why you want to flash t mobile base band on your ATT phone. The ATT BB (at least the BNB4) is fully capable of handling t mobile 4G LTE and other data bands.
What do you mean by "a picture of the broadband page?"

najoor said:
Here is how well it has worked for me so far. I'm in Sweden now and their free sms abroad and unlimited Internet has so far worked as promised (although at data rates close to 100kb/s only which is expected. In the first screenshot I'm turning wifi off and as you can see the phone registers on to the local carrier. In the next screenshot I turned wifi calling on which allowed me to call back to the US for free. There was a half second audio delay but the quality was very good. Finally I attached my home screen shot that shows the T mobile apps that you get after this installation.
So far everything has been working great in the US and in Europe for me but please post your experience here if this has worked for you too.
Click to expand...
Click to collapse
Second screenshot didn't include a blackout on the I.P. Considering you did that in the first screenshot, just pointing out you might want to for the second one as well.
I don't have a Note 3, my dad does. I'm just browsing the forums for an unlock method for SIM for NC(2?) firmware. I like where this one is going. Dad doesn't want me testing sh^& on his phone though, so no luck there. Sorry, but if another tests and claims it works, I'll have all permission to experiment.

SkyAttacksX said:
Second screenshot didn't include a blackout on the I.P. Considering you did that in the first screenshot, just pointing out you might want to for the second one as well.
Click to expand...
Click to collapse
Thanks for pointing that out. The reason I did not mask the second ip address is that in the second picture the phone is on wifi and the ip address is an inside-the-house ip address. These addresses are typical in all internal networks and do not contain any identifying information.

najoor said:
Thanks for pointing that out. The reason I did not mask the second ip address is that in the second picture the phone is on wifi and the ip address is an inside-the-house ip address. These addresses are typical in all internal networks and do not contain any identifying information.
Click to expand...
Click to collapse
Ah, my apologies. ^^

Switched from AT&T to T-Mobile
I switched from AT&T to T-Mobile and wanted to use my 2 Galaxy Note 3's SM-N9000A on T-mobile with all the benefits of T-Mobiles service (e.g. Wi-Fi calling, etc.). Firstly I had to get my phones sim unlocked, and then to find a rom that would port over T-Mobiles rom SM-N900T. After searching diligently to find answers I came across this thread. Najoor helped me get the rom installed (over PM's) and I unlocked the phones (cellunlocker.net under $30), and I am happily an ex-AT&T customer. I like having control over my cell phone plan, which I believe T-Mobile provides. Thanks again Najoor!

The big question still remains: Why? Just to add wifi calling and t mobile app? The 3g bands are still not enabled so it's either 2G, 4G LTE, or 4G. Does this add native wifi tethering? But you can do that with towel root and xposed framework.
I like to keep my AT&T option open, switching between T Mobile(cheaper $45 for 5GB, no tax) and Go Phone(1GB, $45, but better coverage, no tax also), but I recently rooted to take advantage of the tethering which does not work natively on T-mobile since it's an AT&T phone. I can't imagine being on T-Mobile if the signal is so bad that I would need WiFi calling and the t mobile app works just fine on the AT&T Note 3.

Wait so even if I flash another modem I can't enable the 3G bands? I'm pretty sure I just did

Was looking for something like this.
So, the latest TMOBILE based ROM is only jellybean 4.3 ? Is there a kit kat version.
Sent from my SM-N900A using XDA Premium 4 mobile app

monkor said:
Wait so even if I flash another modem I can't enable the 3G bands? I'm pretty sure I just did
Click to expand...
Click to collapse
Look at how to enable the AWS band on the note 3 thread.
http://forum.xda-developers.com/showthread.php?t=2516224
I don't think it has been done. Are you getting 3g in some area? I'm in a good coverage area and only see 4g or 4g LTE. Haven't taken it outside the good coverage area yet but I'm expecting edge only after I leave the 4g area.

I'm having an issuse.
I did exactly what you said, installed safestrap sucessfully, made a rom slot, extracted tweaked whatever, deleted bootstock and bootcolx and vrtheme replaced the two files, installed Tweaked-whatever on that rom slot, deleted Cache, Dalvid Cache, and data and rebooted. It doesn't work. It just gives me a black screen!
What do I do? This doesn't make any sense
EDIT: Didn't realize this thread was dead! Oops!

wifi calling xposed framework
aquaholik said:
The big question still remains: Why? Just to add wifi calling and t mobile app? The 3g bands are still not enabled so it's either 2G, 4G LTE, or 4G. Does this add native wifi tethering? But you can do that with towel root and xposed framework.
I like to keep my AT&T option open, switching between T Mobile(cheaper $45 for 5GB, no tax) and Go Phone(1GB, $45, but better coverage, no tax also), but I recently rooted to take advantage of the tethering which does not work natively on T-mobile since it's an AT&T phone. I can't imagine being on T-Mobile if the signal is so bad that I would need WiFi calling and the t mobile app works just fine on the AT&T Note 3.
Click to expand...
Click to collapse
Hello buddy. I would like to try this method to use wifi calling. Where did you get the mod?

It doesn't work.

Just go to Cricket. $60 a month prepaid unlimited talk, unlimited text, and 10GB of data. All on the AT&T network.

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

I cannot get LTE to any APN work right with any custom ROM on the Moto G4 Play. :(

I have the Moto G4 Play (XT1607) (Harpia) and I have decided to flash LineageOS (lineage-14.1-20170131-nightly-harpia-signed.zip) on it using TWRP v3.0.2 r5. After getting it installed I noticed that it was not connecting to my 4g LTE Internet (I have Ting). So I figured I needed to make some changes to the APN settings. So I go to Settings>... More> Cellular Networks and the moment I click on "Cellular networks" I get an error message saying "com.android.phone has stopped". After reflashing and trying again a few times with the same result, I tried using a completely different ROM. AOKP. (aokp_harpia_nougat_nightly_2017-01-31.zip) and I ran into the same exact problem I was having with LineageOS.
I then tried to see if I could force my way into the APN configuration using an app called "Change APN". This worked, but now I see the message "Access Point Name settings are not available for this user". I decided to ignore this and click on the + to create a new APN. After filling the correct info out for Ting APN, I click on "Save"... and it doesn't save at all.
I decided to revert to the stock rom, and everything works perfectly fine with the stock rom. 4G LTE on Ting works fine. Whenever I try using a custom ROM of any kind, I run into the problem I described above. I don't know if I am forgetting to do something, or completely doing something wrong. I could use some help with this guys.

Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.

mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
Yes. Ting is a Sprint service. Well either way LTE isn't working and the 3G keeps randomly turning on and off whenever I use a custom ROM. However, when I use Stock firmware, everything works perfectly fine. I am unsure what is causing the issue.

It seems nearly all custom ROMs at this point are having data connectivity issues. I'm trying to find a nandroid of the original xt1607 rom so I can just go back until its all sorted out.

mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.

n76 said:
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.
Click to expand...
Click to collapse
I haven't noticed any issue with my GSM ting service on lineage. I get LTE and the WiFi/LTE handoff seems to work. I don't install many apps and don't let them run in the background, so perhaps there's a conflict between them that's shutting down LTE service. This is just a guess.

Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
I looked around in the file system and in /data/data/com.android.phone/ there is no files, no .db files or anything. I don't know of there's supposed to be either. But like OP stated, stock rom is flawless.
Would I be and to copy com.android.phone from stock and restore after flashing? I don't know what to do but this is with every single custom ROM out right now on every release. Data and everything works fine as far as I can tell but just no way to configure the settings. Any help would be greatly appreciated!!!

[email protected] said:
Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
Click to expand...
Click to collapse
Just out of curiosity, have you tried the *22XXX thing yet?
EDIT: Just so we're clear, with you all who have CDMA phones, when you go into "IMEI Information," it does show both an IMEI and an ICCID, right? Because if not, I think I figured out why your LTE isn't working.

I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?

[email protected] said:
I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?
Click to expand...
Click to collapse
It depends on the carrier and the model of the phone. For most Tracfones, it's *22890. For US Cellular, I've seen it as *228 and *22894. You may have to call your carrier and ask what their phone programming code is.

Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)

[email protected] said:
Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)
Click to expand...
Click to collapse
After I posted that, I went back to try and see if Lineage was able to pick up my phone's MEID (even though I use a GSM SIM, the MEID is still tied to the phone hardware). For some reason, Lineage is not reading it, and I think all of your problems are being attributed to that fact.
The way CDMA phones work (and god, do I hate this), is your 2G/3G network is tied to the phone MEID, while the LTE SIM is data only. The OS needs to read both the 14-digit MEID (sometimes shows as a 15 digit IMEI where last digit is 0) as well as the 20 digit ICCID (SIM Number). A phone may also use the SIM number itself as an IMEI (BYOP SIMs do this) by dropping the first five digits of the 20 digit SIM number.
If you phone is showing only one 15 digit number in the system settings, then it's either the MEID OR the SIM, not both. So either you have calling and no LTE, or LTE and no calling. You can't program APN settings because the phone has no idea what ID number to tie APN settings to. This is actually a rather serious conundrum.

Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!

[email protected] said:
Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!
Click to expand...
Click to collapse
I think you just answered your own question. As stated in PCMag back in 2015, "Nobody makes a Dual-Sim phone compatible with Sprint or Verizon." It legitimately believes your MEID is a GSM-based IMEI, and is attempting to cross the streams, so to speak. And the only way your friend's StraightTalk SIM would work is if it was piggybacking off ATT or TMo's networks (the MEID would have been paired to the other phone causing a mismatch).
If you look at the stock ROM for this phone, you will see a BUNCH of system apps for programming Sprint and Verizon network information. They never made it into the custom ROMs we're using. FWIW, here's my thoughts on the matter. Someone needs to go back and make a single-SIM variant of these ROMs, as well as a flashable ZIP containing the necessary APKs for Android to detect the necessary information correctly. And if that doesn't happen, then everyone who bought an XT-1607 has to ditch their carrier and move to a GSM carrier.

That makes complete and total sense! Because I wasn't thinking this while time of it but I was in Oklahoma at the time where the main towers are AT&T, matter of fact Sprint and U.S. Cellular lose almost all signal right when you hit the county line where I was at. Verizon only gets signal because it's Verizon, lol. Reason I say that is because I was wondering why this whole time I has full signal with LTE coverage and completely list everything when I went hone, because where I live is complete opposite, there is hardly any GSM coverage, we don't even have an AT&T store, just Verizon, Sprint, USC.
So, with that being figured out, my laptop just recently kicked the bucket on me so I'm out for the most part, I do have a trick to swap files in and out of a compressed archive without extracting it in any way! But, it takes a while, not too much longer I guess but nowvi just remembered everything is pretty much .dat files so nevermind that.
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.

[email protected] said:
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.
Click to expand...
Click to collapse
IIRC, there is a Verizon thread with 80ish replies, but I think a developer like Squid might need to be made aware of this, so I might copy this into the Lineage thread.

A bit of good news. While reflashing all the time that were force closing when opening cellular networks, I looked in /data/data/com.android.phone/ and was looking, now remember to go back to that directory after I say all this, I found that directory was empty, on all of the Roms. Was curious so I flashed back to stock. Went to the same directory, BOOM! com.android.phone was not empty, in that folder I found 2 folders that were now populated with in:
1: (/files/ )I now had a file named carrierconfig-com.android.carrierconfig- (and after the dash was my ICCID number) so for this directory I need /data/data/com.android.phone/files/carrierconfig-com.android.carrierconfig**ICCID** (replace **ICCID** my ICCID number)
2: then there was this /data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
and
phone/shared_prefs/com.android.phone_preferences.xml
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.

[email protected] said:
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.
Click to expand...
Click to collapse
That is definitely a major find! My only concern is even if you do that, there might be further missing components that would cause Dialer to crash on startup or some other wacky side effect. However, if you can make it work, then it's possible the proper APN settings will load by default and you'll no longer need to change them.
If you can, go into the System Apps on the stock ROM and look for any APKs branded by/with Sprint, VZW or USCellular, or anything CDMA related. They might be necessary for reading the SIM's ICCID.

That's what I was thinking too, and sadly for me I don't really know EVERYTHING to look for so it'll be mostly out of trial and error for me to figure it out. I wish they didn't compress Roms into .dat so I could use a root explorer to swap between tabs rather than copy, flash the rom, paste files and then if that didn't work start all over on restoring stock, so on and so forth. I miss my laptop. =(

Updates?
Has anyone looked into this further? I'm experiencing the same problem with the latest LineageOS nightly. US Cellular Prepaid with an XT1607.
I noticed that in my case i had to skip the Insert Sim thing on 1st boot. It never did whatever it wanted to there. (Maybe because I have no signal or weak roaming where I live?)
I'm seriously considering trying it from an area that I have good service in..

G935V on Android N 7.0 issues with receiving calls/texts [Total Wireless]

I have been going through a weird issue on Total Wireless. When I use Android 6.0.1 and below, I have no issues with my service at all, everything works as it should. The issue comes into play when I use any Android 7.0 ROM, be it official or custom. Outgoing calls/4G data are fine, but I cannot receive any phone calls or send/receive texts. The only way for me to be able to receive calls and send/receive texts is to dial out once. After this, everything works as it should, that is until I reboot. Then I it goes back to the partial working state until I dial out again.
The issue persists whether I am using CDMA/LTE or Global Network modes. I have tried every single possible combination of starting with a fully working 6.0.1 firmware and upgrading through Smartswitch, with and without a full Wipe performed afterwards, doing a full 7.0 firmware flash. The issue is always present, and I am not sure if TW has issues with Android 7.0 or if there is a problem with my account. Their CS is absolutely useless in helping me with the issue, and our chats always end with if I can make a phone call, then the issue is resolved. They don't understand that the issue is still present, but it only crops up after a reboot of my device.
I have tried 3 different SIM cards and they have deleted and re-added/reprovisioned my device/number to their system but nothing seems to help this issue. APN is the usual TRACFONE.VZWENTP. It's really weird that it happens on two separate devices that I activate with my mobile number.
My only thought as to what it could be is maybe some weird provisioning error with the number coming from Verizon. Total Wireless doesn't have any type of VOLTE capabilities on their network, yet I was able to use a rooted Note 4 device and activate Advanced Calling/HD Voice and I believe Wifi calling as well and use it fine on their service. One oddity I noticed is that when the phone is in the initial 'Searching for Service' state on a fresh boot when I dial out while connected to Wifi, sometimes I will see Mobile Network Type change to IWLAN, whereas it usually says LTE. After dialing everything works correctly.
Any ideas on further troubleshooting steps I can take? If nothing can be done, maybe there is some way I can have a boot up script that makes a ghost phone call to any random number and immediately disconnects so I don't have to remember to dial out whenever I reboot my device?
Thanks

I don't have a solution yet, but you're not alone. I have a stock G935V (running Nougat) with Tracfone service running over Verizon's network. Whenever I start up the phone, the phone will indefinitely remain in a "Searching for Service" status until I initiate one phone call. Then the network instantly switches to "Verizon Wireless" and everything works correctly for as long as the phone remains on.
A long phone call with Tracfone and Verizon yielded no solution: They indicated everything is configured correctly in my account. Various replacement SIM cards didn't change anything either.
This issue happens with both stock Samsung S6 phones and the Samsung S7 phone in my household. All are running Nougat.

Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.

dbldown7 said:
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
Click to expand...
Click to collapse
Tracfone tried, half-heartedly, to solve the problem by sending me 3 different sim cards. The problem never went away. I just got in the habit of initiating a call to voicemail whenever I restarted my phone.
The problem went away when I upgraded my S7 Edge to Android v8 Oreo.

I have flashed the Nougat "U" firmware on my Verizon S7 Edge. I had VoLTE, hotspot, HD voice when calling someone on Verizon (but the HD symbol doesn't show on my dialer, only on theirs).
Only issue was that. when I introduced the TW SIM, the APN was auto set for Tracfone (and it wasn't working), so I had to manually change it to the TotalWireless one.
Since then I had received the Oreo upgrade and the following security update... and it's still OK.

Wifi calling not working on G955N (Korean S8+)

Hello all,
Got my G955N in my hands. Followed the threads here to get TWRP installed, used it to install Batman ROM, then used TWRP to flash the AT&T CSC as my provider is AT&T.
In my pull down menu I do have the option for WIFI calling, however whenever I hit it, it fails (seems I can't post pics, so here is the text I get: "Loading, this may take a few moments" then it blinks a few seconds in and repeats. Then it goes to "Please try to set up WIFI calling again later."
I know it's an issue with my phone specifically because my wife's AT&T iPhone7 has WIFI calling working fine (not an ISP issue at home) and I swapped her SIM into my phone and I still got the same error. So it's something with the phone and not likely an account level issue (although maybe? Who knows at this point?)
Also, when I enter the testing menu, I see that "Data Service: Disconnected" which I'm not sure is right? Also, VOLTE Provisioned is not selected, however each time I do select it, it immediately goes back to deselected the moment I navigate away from the testing menu. I can reselect it all day and it still goes back to deselected the moment I move out of the screen.
I've read until my eyes bleed and tried just about everything I could find to try and no joy.
Any ideas?
P.S. got pics if anyone wants me to email them to you for clarity. Guess I'm too new here to be allowed to post pics

To follow up:
Turns out it was an account based issue. Seems AT&T tries to verify the IMEI when attempting to use Wifi calling. So unless registered in the network, it isn't going to work.
And the kicker is, AT&T won't allow Wifi calling or other services with any phone they didn't sell. You can toss in your SIM and use calling, but they won't activate other features if you try to bring your own phone.
So I spent yesterday switching to T-mobile and am now fully functional with all the features of my phone working as they should. AT&T lost me as a customer.