Database Users

[Q] Help with Modem - Model: WIND (SM-N900W8)

I am really new to the world of ROOTING & FLASHING and have already bricked one device. I have followed a lot of information provided by the gurus on here but am at a standstill with my new device as I cannot afford to brick a second one due to my lack of knowledge when it comes to this stuff.
I do not wish to root my device at this time but did read the post talking about "regional" lock. It seems this is only relevant if people unlock their device through the rooting method. Since my device is from WIND Mobile (unactivated) and I purchased an unlock code from cellunlocker.net, I assume I can input my Telus SIM and I would not have to worry about a regional lock? As I understand, the purchased unlock code would supersede the regional lock correct?
As for Telus... When I unlock my WIND device, I assume it will be like my original where Telus voice worked but data was limited with 3G. This was due to the radio band for LTE being crippled in the device. I was told without rooting, I could still use the device with LTE but would have to FLASH the LTE modem through the ODIN software. When I look at the link which provides "flashable" modems, there is nothing there for my specific model.
AllGamer posted a modem (.bin) file for the Puerto Rico modem which supports LTE but confirmed with me this is not a file which can be flashed through ODIN and has to be packaged (or something to this affect). This is all too new to me and so if anyone could provide the steps to FLASH a compatible LTE modem onto my device without rooting so I have LTE support enabled, this would be great!
Thank you!

Issue is resolved. Currently, you cannot just flash the modem and must root and install a custom ROM supporting LTE. Once this device has been out long enough, the possibilities of modification will be greater but for now, my device from WIND works with Telus and has LTE data.

First, Telus, Rogers, Bell, Wind....all these carrier carry the same model of Note3 and running the same ROM
all you have to do is pull out your Wind sim card and do a factory reset. Then put in your Telus Sim card.
Phone will find Telus CSC setting and set it up as Telus phone.
As long your phone is sim unlock with Wind Mobile, any Canadian carrier should be working with your phone
About LTE, maybe there just don't have any LTE signal in the area, or your LTE setting has been turn off.
All you need to do is go into setting check under network and see if the phone is running GSM/CDMA/LTE or GSM/CDMA only, just switch between 2 and you will get your LTE with Telus LTE sim.
You don't have to worry about region code once your purchase unlocked online. region lock only apply when the phone never activate with local sim card and trying to activate with sim card from other countries. Just put in your Telus SIM and setting up the phone. Wind has this phone becuz it support AWS network, it doesn't mean the phone come with different modem!
Since you are not looking to root your phone or anything....there really no need for any flashing!

yuenluv said:
First, Telus, Rogers, Bell, Wind....all these carrier carry the same model of Note3 and running the same ROM
all you have to do is pull out your Wind sim card and do a factory reset. Then put in your Telus Sim card.
Phone will find Telus CSC setting and set it up as Telus phone.
As long your phone is sim unlock with Wind Mobile, any Canadian carrier should be working with your phone
About LTE, maybe there just don't have any LTE signal in the area, or your LTE setting has been turn off.
All you need to do is go into setting check under network and see if the phone is running GSM/CDMA/LTE or GSM/CDMA only, just switch between 2 and you will get your LTE with Telus LTE sim.
Since you are not looking to root your phone or anything....there really no need for any flashing!
Click to expand...
Click to collapse
You are only partially right with your response. Look at my other threads with how to get things functional. First, the phone is the same model for each Canadian carrier but as per the agreements between the carriers and Samsung, specific bands have been crippled. I unlocked my Note 3 so yes, the Telus SIM will be recognized upon a factory reset and will pick up the correct APN settings but since the LTE modem has been crippled, the device is great for voice but has sloooooow 3G data.
In order to get the device working with LTE, you must flash an LTE capable modem onto the device. Since this device is new on the market, no modem (.bin) file has been made flashable. At this point, the only option is to root your phone. Even when rooting and installing the Telus firmware (ROM), this will still not enable LTE as there's a safeguard in the device. Once the phone has been rooted, you must go into the regional settings for the device and select the carrier setting for the ROM you just installed. This will format the device and reboot with your carrier setting thus enabling LTE/WCDMA/GSM (auto connect) within your network settings menu. Only at this point, will you have true LTE capability otherwise, you're using a phone with hindered capabilities. Using Telus on 3G is like driving a Corvette with a Cavalier motor.

cellrama said:
You are only partially right with your response. Look at my other threads with how to get things functional. First, the phone is the same model for each Canadian carrier but as per the agreements between the carriers and Samsung, specific bands have been crippled. I unlocked my Note 3 so yes, the Telus SIM will be recognized upon a factory reset and will pick up the correct APN settings but since the LTE modem has been crippled, the device is great for voice but has sloooooow 3G data.
In order to get the device working with LTE, you must flash an LTE capable modem onto the device. Since this device is new on the market, no modem (.bin) file has been made flashable. At this point, the only option is to root your phone. Even when rooting and installing the Telus firmware (ROM), this will still not enable LTE as there's a safeguard in the device. Once the phone has been rooted, you must go into the regional settings for the device and select the carrier setting for the ROM you just installed. This will format the device and reboot with your carrier setting thus enabling LTE/WCDMA/GSM (auto connect) within your network settings menu. Only at this point, will you have true LTE capability otherwise, you're using a phone with hindered capabilities. Using Telus on 3G is like driving a Corvette with a Cavalier motor.
Click to expand...
Click to collapse
In the case, just download Telus ROM from samsungupdate and flash it with Odin3

yuenluv said:
In the case, just download Telus ROM from samsungupdate and flash it with Odin3
Click to expand...
Click to collapse
LOL :laugh: I have already rooted, flashed the Telus ROM and enabled LTE on my device. It is a little more complicated than what you've suggested but yes, you are partially right. Even with the Telus ROM, you need to ensure you've enabled the radio/modem for LTE capability. Thanks for your suggestions!

[Q] Still no LTE

I have a i9505 running 4.2.2 (UFNB8, DBT CSC) stock, non-rooted. My problem is that I still can't get LTE/WCDMA to display as an available option in Network Mode. Operator is Telenet (MVNO, Belgium). I am in a 4G area, according to the operator my SIM card is 4G capable and my IMEI has been 4G activated. According to them I should be able to connect to the LTE netwrok, but no go. They advised factory reset but I don't want to do that for now as I am not sure it will help. I remember seeing LTE as available when I roam (in roaming my MNC is different though).
Any ideas (apart from rooting and forcing LTE radio on?).
How does the 9505 decide when to turn on the LTE radio? Is it based on getting an LTE signal or is something defined on configuration file level per MCC/MNC...?
Cheers.

OK, I should have searched more. But for future generations' sake, apparently there are two possible reasons:
1. Need a factory reset (still don't understand why?!)
2. Your phone's CSC is not supported on your current carrier's network (apparently this is checked and there's a whitelist of some sort)
In my case it was 1 - I reset and now LTE/WCDMA appears.
Cheers

LS997 - Invalid sim card on Stock (Sprint) based roms

Hi guys,
Was able to get a LS997 in Canada. Carrier used is Fido.
Bootloader was unlocked using Dirty Santa.
When using stock based (sprint) rom, I always get an invalid sim error. This causes the phone/cell data not to work.
When using a lineage based rom, sim works perfectly and I get LTE data.
Is this behaviour normal?
Is there a way to make a non-sprint sim work on a stock rom?
Thanks

Update: Tried the WETA US996 rom on the device. Sim is recognized (since its the unlocked version), but LTE only works if I go in Network Mode, disable Global , enable LTE/GSM/UMTS, then set submode to "GSM/GPRS/EDGE only" or "UMTS/HSPA/HSPA+ Only" , then set it to "LTE/LEgacy 3GPP Multi".
This is a PITA since every time the connection is lost, these steps have to be repeated to get LTE data.
Any suggestion would be greatly appreciated.
I am running stock based rom to get the camera app and use the top screen.
Thanks

You have tried root, install twrp and flash file modem

PjLyTam said:
You have tried root, install twrp and flash file modem
Click to expand...
Click to collapse
TWRP is already installed and the roms used are rooted. I looked but am unable to find radios/modem for the ls997.
If running AOSP based roms I have no problems getting LTE to work.
Aren't the radio/modem separate from the roms themselves, or are they included with could be the reason it glitches like that?

the phone itself is not carrier unlocked thats why you get invalid sim. when you use lineage roms they dont check if phone is carrier unlocked

me2151 said:
the phone itself is not carrier unlocked thats why you get invalid sim. when you use lineage roms they dont check if phone is carrier unlocked
Click to expand...
Click to collapse
Thanks, that's what I thought!
Looking at the LTE specs for both phones:
LS997 : LTE band 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 12(700), 25(1900), 26(850), 41(2500)
US996: LTE band 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 12(700), 13(700), 17(700), 20(800), 25(1900)
Source: http://www.gsmarena.com/lg_v20-8238.php
Fido requires 700 MHz on Band 17, 1700/2100 MHz on Band 4, 2600 MHz on Band 7
Source: http://www.fido.ca/consumer/content/configure-unlocked-device-guide
Bands 4 and 7 are a perfect match, and band 17(700) is a subset of band 12(700), so the LS997 should be 100% compatible.
Source: https://en.wikipedia.org/wiki/LTE_frequency_bands
Would you happen to know which modifications I would have to bring to make it so that I can get LTE working out of the box like Lineage for 997 on a 996 unlocked based rom?
Thanks

Phillis said:
Thanks, that's what I thought!
Would you happen to know which modifications I would have to bring to make it so that I can get LTE working out of the box like Lineage for 997 on a 996 unlocked based rom?
Click to expand...
Click to collapse
You would have to use a us996 unlocked ROM with proper apns for your carrier in the apns list. The file is /system/etc/apns-conf.XML I believe

me2151 said:
You would have to use a us996 unlocked ROM with proper apns for your carrier in the apns list. The file is /system/etc/apns-conf.XML I believe
Click to expand...
Click to collapse
Edited my post above.
APN is properly set automatically on phone. As stated in the first (ERROR: second!) post, I can get LTE working, but need to set GSM/UMTS first then switch to LTE manually, and once the connection is dropped, this procedure has to be done again.

looked at the APN settings, they are the same as described by carrier.....anyone has an idea?

Phillis said:
looked at the APN settings, they are the same as described by carrier.....anyone has an idea?
Click to expand...
Click to collapse
like me2151 said, flash the us996 based rom. Its the unlocked version that will allow sim cards from other carriers to be used.
The ls997 roms are cdma based roms that dont use the sim card for anything but lte and is a locked slot unless device is uicc unlocked by the carrier.
There isnt a method currently to uicc unlock this device without the carrier sending the code to the device.

Team DevDigitel said:
like me2151 said, flash the us996 based rom. Its the unlocked version that will allow sim cards from other carriers to be used.
The ls997 roms are cdma based roms that dont use the sim card for anything but lte and is a locked slot unless device is uicc unlocked by the carrier.
There isnt a method currently to uicc unlock this device without the carrier sending the code to the device.
Click to expand...
Click to collapse
Hello,
I am currently on WETA US996, but as described in the second post, I cannot get LTE to work without disabling it first, switching to GSM/UMTS, then activating LTE.
Once I switch over to Wifi for a period of time, then switch back to cellular data (example: leaving the house), I lose all data and have to disable LTE again, enable GSM/UMTS, then reactivate LTE to get LTE data.

Phillis said:
Hello,
I am currently on WETA US996, but as described in the second post, I cannot get LTE to work without disabling it first, switching to GSM/UMTS, then activating LTE.
Once I switch over to Wifi for a period of time, then switch back to cellular data (example: leaving the house), I lose all data and have to disable LTE again, enable GSM/UMTS, then reactivate LTE to get LTE data.
Click to expand...
Click to collapse
have you tried a dif option such as global? or WGSM Etc? You may need to select a dif option.
 @ME2515 also gave the idea to edit your apns master file in system, so its always holding the apns for your carrier, in theory it would force the device to keep the settings as they become the "default" all the time, vs the devices default auto setting for example.

Team DevDigitel said:
have you tried a dif option such as global? or WGSM Etc? You may need to select a dif option.
@ME2515 also gave the idea to edit your apns master file in system, so its always holding the apns for your carrier, in theory it would force the device to keep the settings as they become the "default" all the time, vs the devices default auto setting for example.
Click to expand...
Click to collapse
Hello,
As explained in previous posts, the APNs are properly configured as per Fido settings automatically on the device. I triple checked to make sure all entries were correct.
LTE does work, but only going through the following steps: Go in Network Mode, disable Global , enable LTE/GSM/UMTS, then set submode to "GSM/GPRS/EDGE only" or "UMTS/HSPA/HSPA+ Only" , wait for a data connection, then change it to "LTE/LEgacy 3GPP Multi". Only then will LTE work, and once I switch to wifi, it won't get any LTE data when I disconnect from Wifi unless I go through that procedure again.

Am I really the only one with this problem?
Triple checked APN, it is correct. It's fetched autmatically from Fido when I connect to the network. Still no LTE unless I do the procedure above.

Reply in case someone encounters this issue. The APN setting for LTE was the culprit. I setup the APN as it it weren't an LTE device following the fido directives (using Fido-core-appl1.apn instead of LTEMOBILE.APN) and now get LTE connection when network is set to global.

Phillis said:
Hello,
I am currently on WETA US996, but as described in the second post, I cannot get LTE to work without disabling it first, switching to GSM/UMTS, then activating LTE.
Once I switch over to Wifi for a period of time, then switch back to cellular data (example: leaving the house), I lose all data and have to disable LTE again, enable GSM/UMTS, then reactivate LTE to get LTE data.
Click to expand...
Click to collapse
when installing wetarom to your LS997, what did you select as your device model in the installer? Unlocked US996 or Verizon VS995

einsteino said:
when installing wetarom to your LS997, what did you select as your device model in the installer? Unlocked US996 or Verizon VS995
Click to expand...
Click to collapse
ouch...that was long ago. I do not remember. I bought an unlocked US996 afterwards and sold the 997. Now with an S9+, which again gives problems..lol

Is it possible to unlock more LTE bands?

Hello, everyone! I was hoping maybe you could give me your opinion on the following issue:
About a year ago I purchased a Moto X Play XT1562 in Europe with dual sim support (Asian ROM). I knew beforehand that I'd probably have limited LTE coverage in my country (Argentina), since the bands used by carriers here are B4 and B28, and XT1562 only supports B28 (which is used mostly for coverage in suburbs and rural areas). Band 4 is the main band used in Argentina for LTE coverage in cities and XT1563 is the model that supports it.
For quite some time I've had the theory that most phones should support more bands than they show, and that the differences between various models of the same phone are there to introduce region restrictions, which in turns means that some LTE bands are disabled and that it should be possible to somehow enable them by tweaking the software. For what I've read, there seems to be some support for my theory: there's a thread in this very same forum which claims that it should be possible to unlock all LTE bands in devices with Qualcomm processors by rooting the phone, installing a custom ROM and kernel and changing a few values.
LINK: https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Now, I'd really want that to be the last thing I try. I've rooted my phone before and I even unrooted it by flashing stock ROM, so I know my way around, but flashing a custom ROM and kernel are things I'd rather not do right now.
So, that brings me to my second theory: since XT1562 and XT1563 are basically the same device, their hardware specifications are the same and only differ in the LTE bands they support... and since LTE bands seem to be software-restricted...
1) Could it be possible to unlock Band 4 by flashing XT1563 stock ROM to my XT1562 Moto X Play?
2) Has anyone tried to do that (even by mistake) without bricking the device?
3) If there's no option but to flash a custom ROM and kernel, does anyone know for sure if LTE bands in Moto X Play are software restricted? Or is there a hardware limitation?
Probably my secornd theory won't work because I don't think the solution would so simple, and there would be threads about it... but I guess I don't lose anything by asking
Thank you!! =)

Just realized this thread shouldn't go in General. Could someone please move it to Q&A? Thanks!

The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.

DragonClawsAreSharp said:
The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.
Click to expand...
Click to collapse
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.

floydian86 said:
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.
Click to expand...
Click to collapse
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.

DragonClawsAreSharp said:
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.
Click to expand...
Click to collapse
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.

floydian86 said:
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.
Click to expand...
Click to collapse
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .

DragonClawsAreSharp said:
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .
Click to expand...
Click to collapse
I did try to select LTE only, but it didn't work.
I also tried using service menu, but I didn't find any of the tests to be useful to check which LTE bands are supported.
About the scenarios you propose, I also thought maybe all I achieved was to restrict LTE bands to the ones supported by both models :S. At work my phone picks band 28, but both models support it, so there's no way to check it by discarding...
There's a third possibility, though, which is that both models' modems are exactly the same and bands are only limited by NV.
After work I'll see which custom roms and kernels are there for X Play and start studying the process to edit NV. Still it might not be possible to do so because the post claims that rom and kernels must be compiled from source code, so the ones made from stock won't work... That means I depend on there someone making a rom and kernels that meet those requirements.
In the second link, the person says he can't save the changes he makes to the NV, which is what is supposed to happen if you're using stock rom and kernel, according the link I've shared.

So, I ended up editing the NV in order to remove Band 4 restriction. It took me a while because I had to figure out how to bypass all the obstacles I found on the way but, once everything was set up, the process was quite simple.
I had to boot my phone in BP Tools mode and configure the QC Diag port driver correctly. Also, I had to use a newer version of QPST because the one I donwloaded first didn't work.
The tutorial claims that your phone must be rooted and that you need a custom rom and kernel in order to avoid the "anti-tamper" mechanisms in newer Qualcomm devices. My first approach was not to do such things (i.e.: unrooted phone with stock rom and kernel).
I edited the NV values as suggested in order to enable Band 4. The good news are that the custom values that I added didn't revert back to the original ones after I rebooted and also that I didn't brick my phone and it's working properly
Right after I rebooted my phone, it picked 4G signal, but after just a few seconds it switched to H. I forced my device to LTE only, and it connected to 4G, but then again it completely lost signal. My phone does pick LTE Band 28 sometimes, but not at my place, so I thought that I must have been picking up Band 4 (I tried to leave it set to LTE only, but it picked no signal at all).
Also, when I'm at work, it sometimes picks Band 28, but signal must be very weak because it never lasts more than a few minutes, after which goes back to H.
So far I'm not sure if the mod worked because I can't find a way to see which bands my phone currently supports or which LTE band it's connected to. I tried an app called LTE Discovery, but it labels it as "unknown band" (I suspect that my phone needs to be rooted in order for that feature to work).
Right now, I'm thinking of three possible things that could have happened:
1) The mod worked and LTE signal is just very poor by my place.
2) It worked and it connected to Band 4 for a few seconds, but then the anti-tamper mechanism detected that situation and software-blocked it (without reverting NV changes I made). In this case, I'll have to flash a custom kernel and see what happens.
3) There's a hardware limitation after all, in which case there's nothing I can do (I don't think this is the case)
Right now I'm at work and my phone has been picking up 4G for over an hour already. Since it usually only lasts a few minutes (connected to Band 28), then I guess there are reasons to be optimistic that it worked after all and it is currently using Band 4.
If I succeed, I'll open a new thread with a tutorial for Moto X Play.

I'll keep updating my progress on the issue in order to leave a record of everything I tried. Also, it could be helpful to other people who are trying to do the same thing or maybe someone who has done this before will see this and point me in the right direction . Again, if I succeed I'll write a more detailed guide.
I can confirm that what I did so far didn't work, I've modified the necessary NV values and even flashed Squid kernel, but still no success: I'm definitely not picking Band 4 anywhere, only Band 28.
While flashing the custom kernel, I also wanted to use the opportunity to root my phone, but for some reason I soft-bricked it in the process, so I had to flash XT1562 stock rom again (with XT1563 modem). This reverted the NV values to the default ones, so I had to customize them again.
The user fffft says that custom rom and kernel are needed in order to avoid the anti-tamper code, but also that it is most likely in the kernel. I could try another kernel, maybe Phoenix, but if that doesn't work either, then we can confirm that the anti-tamper code is actually in stock rom.
This leaves three final possibilities to succeed in unlocking LTE Band 4:
_Flashing another custom kernel
_Flashing a custom rom
_Flashing the whole XT1563 stock rom, as I proposed at first, and see what happens. If this works, this should both set the NV values to enable XT1563 default LTE bands (which includes Band 4) and also set a different anti-tamper code, which should not bother. Worst case scenario I'll soft-brick my phone again and I'll have to flash XT1562 rom.

Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up

floydian86 said:
Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up
Click to expand...
Click to collapse
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.

DragonClawsAreSharp said:
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.
Click to expand...
Click to collapse
Thanks!
When I edited the NV, the changes were saved (I closed QPST and QXDM, then rebooted my phone and checked the values). However, when I flashed stock rom, the values reverted to the original ones. I also thought that shouldn't happen, but nevertheless it did :S
About getting Diag mode on custom roms, I took a quick look at developer options but I didn't see anything useful. I read a few posts that claim it can be done using a terminal emulator, so there has to be a way around it.
The steps you mention are the ones I had in mind, except for rooting. Do you think it's really necessary? (phone will be rooted after flashing custom rom, anyway).
I'll try it tonight and see what happens =)
EDIT 1: If I understood correctly, step 14 of the thread I've shared is only for 3G bands, so I don't need to change anything there. LTE bands NV's can only be seen and modified using QXDM and that's where I checked if the changes were saved. However, I have seen that there are a few holes in the tutorial, some of which I had to figure out myself. Maybe there's one extra step I'm missing on QPST? Step 24 seems to indicate otherwise.
EDIT 2: I've found this thread. It's about a Lenovo phone, but chances are they are the same: http://www.teamsuperluminal.org/forums/topic/open-diag-port-in-cm-12-1-for-qpst/
This is what it says: "To open the diag port, connect the phone to a PC and use ADB:
adb shell
su
setprop sys.usb.config diag,adb"

Changing the NV and then flashing custom ROM didn't work (I deleted system, data and cache before but still didn't work).
I tried enabling diag mode using ADB with the code I found but it didn't work. No diag port gets enabled.
I'm ready to give up. It seems it can't be done, at least not on X Play
Unless maybe someone know how to use diag mode on Moto X play running Cyanogenmod?

XT1687 3G only on VZW and phone ICCID unknown

Hi all,
I picked up a used G5 Plus (XT1687) on eBay, with the bootloader already unlocked. I immediately installed AICP ROM with a VZW SIM from a working G4. The phone showed LTE for data, but no voice service. That started a long series of firmware changes that saw me trying Pixel Experience, and a few stock ROMs, having my IMEI show as 0 a few times as well.
I'm at a point with the phone now where I'm on the latest retus channel stock ROM (POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with the bootloader locked. The phone now connects with 1xRTT for voice and EvDo (3G) for data. If I swap this SIM into my other phone (Pixel XL) I get full LTE in the Pixel but still 3G only in the G5+.
The only other standout item is in the BP tools SIM menu, where I get the following errors.
Phone ICCID Compare with SIM ICCID: ERROR
and
PHONE ICCID: PHONE_ICCID_UNKNOWN
I feel like with all the flashes I may have really screwed things up. does anyone have any recommendations on what to try to get LTE service back?
TIA!

I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.

[email protected] said:
I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.
Click to expand...
Click to collapse
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk

bra1niac said:
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It seems they would rather replace than fix.

Same with my phone. It has been unlocked and I've been on numerous variations of ROMs stock and custom. Everything was smooth with no issues until I decided to flash an Oreo 8.1 ROM. Immediately after I was greeted with 3G EVDO-Rev A./1xRTT mode with no access to 4G/LTE on Verizon. Sim Card status is screwy with some apps seeing it, albeit improperly configured, most not able to detect it at all. If I return to any ROM below 8.1 I have no data service whatsoever. Hoping a fix is found as all the workarounds do nothing.
Also like the OP, I can get LTE to stick sometimes by messing around with Radio Bands and switching options around in the 4636 menu. But that leaves me without voice/text/mms service.

[email protected] said:
It seems they would rather replace than fix.
Click to expand...
Click to collapse
sad but true
Sent from my Pixel XL using Tapatalk

I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.

[email protected] said:
I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.
Click to expand...
Click to collapse
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.

bra1niac said:
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.
Click to expand...
Click to collapse
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me
this zip will "erase" format the modem status partition:
mdm1m9kefs1 = modemst1
mdm1m9kefs2 = modemst2
Click to expand...
Click to collapse
Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.

[email protected] said:
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.
Click to expand...
Click to collapse
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.

It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.

Archangel said:
It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.
Click to expand...
Click to collapse
yeah a factory Oreo ROM would probably help straighten a bunch of things out.
Sent from my Pixel XL using Tapatalk

bra1niac said:
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.
Click to expand...
Click to collapse
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.

A little research into the baseband processor and its radio firmware RTOS [real-time operating system,] shows it to be closed source, proprietary, yet full of flaws. It is even susceptible to the long standing "Hayes command set" but I don't believe this to be where our particular problem lies. Because it is so closed, it is doubtful the Oreo roms were able to inadvertently touch anything inside this secondary operating system all phones have. It is more likely it is the communication between our android firmware, and the radio firmware, but why the restoration back to stock, doesn't remedy it, is a mystery. The devs that adapted the Oreo roms to this device, missed this link or they would not have written to that area, I'm sure.

You guys are a lot smarter than me,,,it just scared the heck out of me. I flashed a 8.1 rom like I have done at least a dozen or so times on this phone and then suddenly no signal at all,,,then just 4g data and no voice service. I went back to a 8.1 back up that I have and within a few mins everything came back. Now, I am afraid to flash anything rom wise for fear of not getting any signal back.

Something like this really deserves an official statement by Lenovo, Motorola or Verizon. Even if that statement is an unfortunate "you knew the risks associated with unlocking the bootloader and flashing ROMs / modems". Even if none of the three know what exactly is going on they should at least let us know.
Is this problem something that happens with all carriers and their LTE signals? Am I right in thinking that using Verizon is currently the only carrier in which the issue can't be fully repaired?
I havent yet restored my partially working (3g/1x) EFS backup to a stock Nougat Rom yet as I want to have 4G working as well if I do that. If the other carriers can be fully repaired I'll just switch carriers until I get a new phone.

There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.

[email protected] said:
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.
Click to expand...
Click to collapse
Yeah that all seems to make sense. Something we broke with a software change should be fixable with a software change. Hopefully the next OTA isn't too far away.

[email protected] said:
There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.
Click to expand...
Click to collapse
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:

bra1niac said:
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:
Click to expand...
Click to collapse
It might pay to remove your sim, flash the
Code:
fastboot erase modemst1 fastboot erase modemst2
and then insert her sim. I'm just thinking that would clear the modem for the new bands to set themselves.