Database Users

Reset radio band

Ok I really derped hard. I use the *#*#4636#*#* menu to change my network type between 2G,3G and LTE as needed. The one under Cellular Network Settings doesn't work all the time as it chooses the selected type as 'preferred' whereas the service menu forces it.
I don't know why I did it, I went to the 3 dot menu in the hidden service menu and chose "Select radio band" and clicked on USA band which was the first option. [DO NOT TRY THIS ,THERE'S NO WAY TO REVERT]. I'm not in the US and now I've lost signal reception on my phone and since then I've flashed the radio image numerous times from the bootloader, even flashed my bootloader,radio,boot image,cache,system all over to no use. I am not getting any signal on my phone. I had done the same once on my Nexus 5 but don't remember what I did to fix it. I'm still trying everything I can think of. A full factory reset didn't help either. The SIM card is fine,I tried it on another phone. Please help.

maybe try flashing an older image. and then see? Also check the nexus 6 forums, I believe someone did something similar and i assume found a fix.

Were you ever able to figure out how to fix this? I ran into the same issue.

If you are on Verizon, select Band 6 on that Menu & let your phone sit for 10 minutes so that it register on the network again with new settings.

sayazs said:
Were you ever able to figure out how to fix this? I ran into the same issue.
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showpost.php?p=64083667&postcount=14
I ended up replacing my device from my retailer.

Nexus 6p Can't make or receive calls

Hello Everyone,
Happy new year.
I recently received a nexus 6p model H1511 from ebay. everything works normally except sending and receiving calls.
I live in Qatar btw and I'm struggling to fix this issue. Anyone knows how to solve it?
Texting in and out works perfectly.
LTE data is working smoothly.
Only issue is making and receiving calls.
Appreciate your help
Thanks
Mohamad
edit >> Problem solved .. read my last comment
Thanks @scoobysnack the hero
Thanks @Exec360
Thanks @Soulfly3

mohawahba said:
Hello Everyone,
Happy new year.
I recently received a nexus 6p model H1511 from ebay. everything works normally except sending and receiving calls.
I live in Qatar btw and I'm struggling to fix this issue. Anyone knows how to solve it?
Texting in and out works perfectly.
LTE data is working smoothly.
Only issue is making and receiving calls.
Appreciate your help
Thanks
Mohamad
Click to expand...
Click to collapse
Sounds like someone switched your radioband. You might ask how do you know this. Well I was playing with my phone yesterday and did just that. I had data and was able to send SMS but unable to make calls. I was able to fix this by reflashing my phone to stock and using dialer code *#*#4636#*#* go to "phone information" click the 3 dots in upper right and select "radio bands". I used band 6 so you might want to try band 8. Hope that solves your problem. Also please anyone who reads this DO NOT mess with the band settings it will screw up your phone. I am not responsible for any damage to your phone if anyone tries this. This is just how I fixed my phone and offer it at a suggestion to get this gentleman's phone working again.
---------- Post added at 03:44 PM ---------- Previous post was at 03:34 PM ----------
I forgot to mention I flashed back to 6.0.0 if your not on a custom ROM try the dialer coded without flashing and see if that fixes your problem.

scoobysnack said:
Sounds like someone switched your radioband. You might ask how do you know this. Well I was playing with my phone yesterday and did just that. I had data and was able to send SMS but unable to make calls. I was able to fix this by reflashing my phone to stock and using dialer code *#*#4636#*#* go to "phone information" click the 3 dots in upper right and select "radio bands". I used band 6 so you might want to try band 8. Hope that solves your problem. Also please anyone who reads this DO NOT mess with the band settings it will screw up your phone. I am not responsible for any damage to your phone if anyone tries this. This is just how I fixed my phone and offer it at a suggestion to get this gentleman's phone working again.
---------- Post added at 03:44 PM ---------- Previous post was at 03:34 PM ----------
I forgot to mention I flashed back to 6.0.0 if your not on a custom ROM try the dialer coded without flashing and see if that fixes your problem.
Click to expand...
Click to collapse
I will try and feedback you soon. Thanks for your help ..

link to another post that may help you (similar to above) http://forum.xda-developers.com/nexus-6p/help/nexus-6p-calling-issues-make-calls-data-t3270877/post64352966#post64352966
Just ignore the Verizon stuff, as you're not on verizon
Really hope it isn't a EFS/IMEI issue... if it is, the guy sold you a lemon (most likely)... repairing that without a backup is near impossible.

Soulfly3 said:
link to another post that may help you (similar to above) http://forum.xda-developers.com/nexus-6p/help/nexus-6p-calling-issues-make-calls-data-t3270877/post64352966#post64352966
Just ignore the Verizon stuff, as you're not on verizon
Really hope it isn't a EFS/IMEI issue... if it is, the guy sold you a lemon (most likely)... repairing that without a backup is near impossible.
Click to expand...
Click to collapse
I just found another thread here on page 2 and they have the same answer. I didn't see it yesterday when I screwed my phone up.

(can't find the thread) but someone in a similar boat said they did a factory reset, and then re-installed the bootloader and it fixed their issue.
but Id try to find that thread and knwo EXACTLY what you're doing before going down that path

Soulfly3 said:
(can't find the thread) but someone in a similar boat said they did a factory reset, and then re-installed the bootloader and it fixed their issue.
but Id try to find that thread and knwo EXACTLY what you're doing before going down that path
Click to expand...
Click to collapse
I tried restoring the radio and bootloader it did not work for me

Well, let's hope for this guy's sake, the seller didnt screw up the EFS/IMEI, leaving him w a data only phone.

Soulfly3 said:
Well, let's hope for this guy's sake, the seller didnt screw up the EFS/IMEI, leaving him w a data only phone.
Click to expand...
Click to collapse
That would suck...I wish him lots of luck.

scoobysnack said:
Sounds like someone switched your radioband. You might ask how do you know this. Well I was playing with my phone yesterday and did just that. I had data and was able to send SMS but unable to make calls. I was able to fix this by reflashing my phone to stock and using dialer code *#*#4636#*#* go to "phone information" click the 3 dots in upper right and select "radio bands". I used band 6 so you might want to try band 8. Hope that solves your problem. Also please anyone who reads this DO NOT mess with the band settings it will screw up your phone. I am not responsible for any damage to your phone if anyone tries this. This is just how I fixed my phone and offer it at a suggestion to get this gentleman's phone working again.
---------- Post added at 03:44 PM ---------- Previous post was at 03:34 PM ----------
I forgot to mention I flashed back to 6.0.0 if your not on a custom ROM try the dialer coded without flashing and see if that fixes your problem.
Click to expand...
Click to collapse
I really appreciate your efforts .. I did return to the stock rom .. the original 6.0.0 and it did not help. when i try to dial any USSD, it gives me MMI error .. i dunno if it is related to EFS/IMEI as u said. Plus dialing *#*#4636#*#* , i find only USA band, Band 6 & 7 only ..
a friend of mine bought the same model from amazon and he has the same band when dialing the above code, he also have the same bands ( USA, 6, 7 ) like me and his phone is working fine here ..
What do you suggest? it's an EFS/IMEI issue ?
Thanks a lot. I really appreciate your concern. the problem is I can't return it ...

Did you select a band? Of you don't click one of the options it will not change.

scoobysnack said:
Did you select a band? Of you don't click one of the options it will not change.
Click to expand...
Click to collapse
I did choose usa band and nothing .. i feel it is a problem with the carrier recognizing the phone

I'm starting to lean towards this being an EFS/IMEI issue.
Research is all I can offer at that point... exhaust everything beforehand, because EFS issues are nearly impossible to repair, unless you have a backup, which you dont.

mohawahba said:
I did choose usa band and nothing .. i feel it is a problem with the carrier recognizing the phone
Click to expand...
Click to collapse
I think I would try band 7 just in case. Does your network show up in the to left corner?

scoobysnack said:
I think I would try band 7 just in case. Does your network show up in the to left corner?
Click to expand...
Click to collapse
yea .. everything is working fine except the calls. I can send receive text and LTE
carrier name is apparent on the left corner ..
btw I tried calling google support and they said we have nothing to help you with

Soulfly3 said:
I'm starting to lean towards this being an EFS/IMEI issue.
Research is all I can offer at that point... exhaust everything beforehand, because EFS issues are nearly impossible to repair, unless you have a backup, which you dont.
Click to expand...
Click to collapse
but the guy u shared me his link could solve it .. however he is ok verizon .. i believe it has something to do with my carrier ?
maybe the phone is not recognized right? but when i tell this to myself, i quickly come to a point if the carrier unable to recognize my IMEI right, would texts and LTE work ?
GSM is in service when i check phone information by *#*#4636#*#*
huawei technical support in Qatar would help if i gave them the fone ?

mohawahba said:
but the guy u shared me his link could solve it .. however he is ok verizon .. i believe it has something to do with my carrier ?
maybe the phone is not recognized right? but when i tell this to myself, i quickly come to a point if the carrier unable to recognize my IMEI right, would texts and LTE work ?
GSM is in service when i check phone information by *#*#4636#*#*
huawei technical support in Qatar would help if i gave them the fone ?
Click to expand...
Click to collapse
Try band 6 or 7 but I would lean towards band 7. I don't think your carrier name would show up if it were a bad EFS or IMEI.

SOLVED
scoobysnack said:
Try band 6 or 7 but I would lean towards band 7. I don't think your carrier name would show up if it were a bad EFS or IMEI.
Click to expand...
Click to collapse
Nailed it. Problem solved.
Installing Chroma ROM solved the issue because basically it was a problem of bands. Chroma had more bands that work in Qatar. and I could return back to stock rom again without any problems ( but don't mess up with bands in phone information )
I had to choose Aus band to make it work here in Qatar.
Band 6 and 7 and USA did not work for me. Chroma ROM had more bands that helped me to tangle this issue.
Thanks buddy @scoobysnack for helping me out.. I would solve it without your assist. I owe you a bag of marshmallow

No problem. It was my pleasure to help you. I told you installing chroma would fix your issues

scoobysnack said:
No problem. It was my pleasure to help you. I told you installing chroma would fix your issues
Click to expand...
Click to collapse
Hi. Would you be able to walk me thru on installing Chroma? Same issue here. Calls work under 3G but if I choose preferred network type LTE(recommended), data and texts only work. Calls do not.Im from the Philippines btw.
I tried to access hidden test menu, radio bands available are only United States, Cellular 800, PCS and Class 10 (800Mhz Secondary)
Preferred Network type is LTE/CDMA/UMTS auto (PRL)

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

Verizon Essential stuck in 3G after the upgrade

Before I updated via OTA to 8.1 the Essential was connecting to LTE without issue. Since 8,1 I have to connect to CDMA and 3g in order to user my Dialer, otherwise Server Error is generated. No calls in or out.
I wanted to downgrade Yes rebooted, factory reset, etc.
I searched google up and down with no real answers that work. How do I get Sideload working again? It has to be a simple configuration or driver problem I will assume.
Thanks

Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....

Exxeviant said:
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506

wolfu11 said:
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
Click to expand...
Click to collapse
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.

Bigdny said:
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Click to expand...
Click to collapse
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).

wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached

wolfu11 said:
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
Click to expand...
Click to collapse
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.

wolfhelm said:
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
Click to expand...
Click to collapse
Yeah I've screwed with this phone so much I don't know what I did LOL but now it shows wifi calling even in dialer. I'm not sure if it really works cuz I have a good signal so it never switches. My e911 address is set up from my Moto z and I do have a wear24 watch tied to this phone not sure if that's what triggered it. ? I did get a new SIM card on Monday as well because I was fighting with the vzw crap so I don't know exactly what triggered the WiFi calling.

wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.

Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?

wolfhelm said:
Are you on 8.0 or 8.1?
Click to expand...
Click to collapse
I upgraded to 8.1 via OTA. No root, no rom.

Bigdny said:
I upgraded to 8.1 via OTA. No root, no rom.
Click to expand...
Click to collapse
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.

wolfhelm said:
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
Click to expand...
Click to collapse
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?

tech_head said:
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
Click to expand...
Click to collapse
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.

wolfhelm said:
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
Click to expand...
Click to collapse
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.

tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
That's a good point, I have reported as well.

tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
Doing the same right now. Just glad Im not the only one having the problem.

Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Try turning off Enchanted 4G LTE Mode. It's possible going to 8.1 just reset this setting to on. This should only be on if you have HD Voice enabled on your line on Verizon (you'll have to call Verizon to enable it, it's a free feature).
This should fix server error on 4G, randomly connecting to Sprint is a separate issue.

UPDATE Now working
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.

Bigdny said:
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Click to expand...
Click to collapse
Just wanted to second this post that a new sim card is the key to solving this issue. In my case, I was using Red Pocket CDMA (VZW network), and I ran into the same problem. Red Pocket rep explained to me that my sim got provisioned to 3g only and that I needed a new sim to connect to LTE. As soon as we switched to a new sim, I got LTE. I hope this helps others.