• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[FIRMWARE][GUIDE] Restoring Moto E4 (xt1766) (Qualcomm) SPerry to Stock Factory State

Search This thread

MotoJunkie01

Senior Member
Apr 2, 2016
2,403
1,213
Corbin
--- QUALCOMM ONLY ---
Motorola Moto E (4th Gen) SPerry xt1766
Stock Android 7.1.1 Factory Firmware
Build No. NCQS26.69-64-10
Blur_Version.26.231.8.sperry_sprint.sprint.en.US
Restoration & Firmware Flashing Guide

WARNING: by proceeding further, you are assuming full responsibility for the integrity and operability of your device. Although this firmware package has been fully tested on my own device, I am not responsible in the event something goes wrong. Follow the comprehensive instructions and things should go smoothly and without incident.

Thanks & Credit:
Once again, I owe credit and give an abundance of thanks to XDA member @ALI12 for so graciously providing this needed firmware package. His RSD Lite firmware thread for this build is here https://forum.xda-developers.com/mo...tock-rom-moto-e4-sprint-ncqs26-69-64-t3852464
I would respectfully ask any members who use this firmware to thank @ALI12 on the above thread.

CHANGELOG:
This firmware update brings standard bug fixes and stability improvements, as well as security patches up to September 1, 2018. Please note that the radio firmware (baseband version) was not updated from the previous firmware build, and remains at version M8920_15000.280.06.58.05R. However, the radio firmware did receive some minor patches to improve cellular data handover whenever a WiFi connection loses internet access or becomes unstable. Patches were also added to update the PRL databases.

SPECIFICATIONS:
Device Name: Motorola Moto E (4th Gen)
Compatibility: xt1766 SPerry (Qualcomm)
Provider(s): Sprint, Boost Mobile, Virgin Mobile
Android Version: 7.1.1 Nougat
Build No. NCQS26.69-64-10
System Version: 26.231.8.sperry_sprint.en.US
Bootloader Version: moto-msm8920-BB.32
Radio Version: M8920_15000.280.06.58.05R
Kernel Version: 3.18.31-perf
FSG Version: FSG-8953-11.22
Build Date: August 28, 2018
Security Patch Level: September 1, 2018
Package Size: 1.55 GB

APPLICABILITY:
Flashing this firmware package via the instructions below will restore your device to the default stock factory configuration. Also, your device will be up to date with the latest firmware version. All files, media, etc., stored on your device will be erased, so please make a suitable backup of anything important prior to proceeding. Flashing this package will enable dm-verity (device mapping), force encryption of the /userdata partition, and will remove any modifications such as root binaries, BusyBox, Xposed Framework, etc. Also, if you have a custom recovery installed, such as TWRP, it will be replaced with the stock recovery. Upon reboot, your device will be fully capable of installing any future OTA update packages as well.

INSTRUCTIONS:
This guide assumes that you already have the most current version of Minimal ADB and Fastboot utilities installed on your PC or laptop, as well as the most current version of Motorola Device Manager (to ensure current USB device drivers are installed on your PC/laptop). It is also assumed that you have at least a rudimentary understanding of AP Fastboot Mode and executing fastboot commands. While this package may be installed using alternative methods such as mFastboot or RSD-Lite, this guide focuses on a standard fastboot command set. Also, it should be noted that I have only tested this package on a device with the bootloader in an unlocked state. While, in theory, a factory firmware package should flash to a device with a locked bootloader, I have not confirmed on this package.

NOTE: Flashing this firmware package to an OEM unlocked device does not re-lock the bootloader. Also, contrary to popular belief, your bootloader does not need to be in a locked state in order to install an OTA update package. The state of the bootloader has no significance with respect to OTAs. As long as your device has been flashed/restored with a factory firmware package -- such as this one -- OTA updates will install properly.

1. Download the firmware package from the below link and extract the contents of the archive to your ADB/Fastboot directory on your PC;
2. Power off your device, then hold the Power + Volume Down buttons simultaneously for 7 - 8 seconds until AP Fastboot Mode appears on your device display;
3. Connect your device and PC using the OEM supplied, or quality equivalent, micro USB to USB charge/sync cable;
4. Open a command prompt window in the path of your ADB/Fastboot directory. Execute the following command:

fastboot devices

If properly connected, your command prompt window will return an alphanumeric string synonomous with your device serial number;
5. Once a proper connection has been confirmed, execute the following commands, preferably in this order:

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear

Reboot your device by executing:

fastboot reboot

Upon reboot, your xt1766 should now be restored to stock factory condition and running on the latest firmware build version.

DOWNLOAD LINKS:
Android 7.1.1 -- NCQS26.69-64-10: https://drive.google.com/file/d/1H5V6ZUHWhSrBn1_8pHq8_qrwiXYga2YC/view?usp=drivesdk



PREVIOUS FIRMWARE BUILDS:
Android 7.1.1 -- NCQS26.69-64-8:
https://drive.google.com/file/d/1CG9Bb2csn2dWLy1jfP0yimhVpMq-NDub/view?usp=drivesdk

Android 7.1.1 -- NCQS26.69-64-5:
https://drive.google.com/file/d/1ZoACEF5-lruTu4yhGknKjUqdXxGTf7kQ/view?usp=drivesdk
 
Last edited:

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
The people with this phone unlocked gsm using it in other country or not using Sprint just don't upgrade the phone never ever stay with the original firmware that comes by default with the phone because the new versions of the stock firmware don't let you add or edit the Apn's or even use Hotspot , the version of stock that let you edit apn is ncq26.69-48 people should know this already that's why there are so many people bricking their phones trying to downgrade i already owned 2 Moto e4 and never had problems with default stock rom I just disable Motorola Update Service App and never get bother again with system updates for other people this post is useful don't know who but it is I don't recommend upgrading. Thanks.
 

MotoJunkie01

Senior Member
Apr 2, 2016
2,403
1,213
Corbin
The people with this phone unlocked gsm using it in other country or not using Sprint just don't upgrade the phone never ever stay with the original firmware that comes by default with the phone because the new versions of the stock firmware don't let you add or edit the Apn's or even use Hotspot , the version of stock that let you edit apn is ncq26.69-48 people should know this already that's why there are so many people bricking their phones trying to downgrade i already owned 2 Moto e4 and never had problems with default stock rom I just disable Motorola Update Service App and never get bother again with system updates for other people this post is useful don't know who but it is I don't recommend upgrading. Thanks.
Downgrading is typically never an issue unless sensitive bootloader partitions are downgraded or attempted to be downgraded. But this is nothing new. Motorola Mobility has included downgrading safeguards on most of their smartphones since at least 2013. Unfortunately, however, Motorola does not routinely release QPST blankflash files so that users can repair hard bricked devices.
As far as upgrading, I am running the most current version of firmware (NCQS26.69-64-5) and have no problem switching to a custom ROM for use with any GSM network. I'm actually using AT&T on my xt1766 Moto E4 right now.
 
Last edited:

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
Downgrading is typically never an issue unless sensitive bootloader partitions are downgraded or attempted to be downgraded. But this is nothing new. Motorola Mobility has included downgrading safeguards on most of their smartphones since at least 2013. Unfortunately, however, Motorola does not routinely release QPST blankflash files so that users can repair hard bricked devices.
As far as upgrading, I am running the most current version of firmware (NCQS26.69-64-5) and have no problem switching to a custom ROM for use with any GSM network. I'm actually using AT&T on my xt1766 Moto E4 right now.

And Can The Apn Area Can be edited and Add or Delete new apn settings >? and Use The hotspot ? a lot of people has this problem including me with my other E4 and i had to downgrade

---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------

i can use my moto with stock firmware on any gsm network here in my country without use custom roms.
 

MotoJunkie01

Senior Member
Apr 2, 2016
2,403
1,213
Corbin
And Can The Apn Area Can be edited and Add or Delete new apn settings >? and Use The hotspot ? a lot of people has this problem including me with my other E4 and i had to downgrade

---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------

i can use my moto with stock firmware on any gsm network here in my country without use custom roms.
The APN settings can be edited on any Android 7.1.1 stock build for the xt1766. With root access and a root file editor, the apns-config.xml file can be modified/edited.
 

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
With the original Stock that comes with the phone by factory NCQS26.69-48 there is no need of root for any APN edit on Settings.
 

MotoJunkie01

Senior Member
Apr 2, 2016
2,403
1,213
Corbin
With the original Stock that comes with the phone by factory NCQS26.69-48 there is no need of root for any APN edit on Settings.
Correct. As you have pointed out, NCQS26.69-48 appears to be the only build that permits an APN to be added/edited directly from Settings>Mobile Networks. On subsequent builds it is necessary to edit the apns-config.xml file from the root filesystem.
 

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
Well I was Preparing To Upgrade Because I was Intrigued What Can Do My Phone With New Software And Edit /etc/apns-config.xml like you said to add apns and i was making a backup of my Actual apns-config.xml File but then i started Searching And Finding The Custom APN'''s entries I made With Custom Names and Everything on Settings>Mobile Networks and guess what there is NONE of them on apns-config.xml So this means is not going to work like that , i dont think that custom apns are inserted in the file in question so No Upgrade for me also im using a custom kernel with the f2fs patch to pass SafetyNet with Magisk which is based on the NCQS26.69-48 kernel source but i was going to leave all that behind just to upgrade , No GO for me . Can The Bootloader be Locked With this signed OEM Firmware just asking :> , I hope Oreo 8.1 Roms Come To Moto E4 ................. soon.
 

MotoJunkie01

Senior Member
Apr 2, 2016
2,403
1,213
Corbin
Well I was Preparing To Upgrade Because I was Intrigued What Can Do My Phone With New Software And Edit /etc/apns-config.xml like you said to add apns and i was making a backup of my Actual apns-config.xml File but then i started Searching And Finding The Custom APN'''s entries I made With Custom Names and Everything on Settings>Mobile Networks and guess what there is NONE of them on apns-config.xml So this means is not going to work like that , i dont think that custom apns are inserted in the file in question so No Upgrade for me also im using a custom kernel with the f2fs patch to pass SafetyNet with Magisk which is based on the NCQS26.69-48 kernel source but i was going to leave all that behind just to upgrade , No GO for me . Can The Bootloader be Locked With this signed OEM Firmware just asking :> , I hope Oreo 8.1 Roms Come To Moto E4 ................. soon.
You're completely right. I recall now that apns-config.xml is not the only file needing editing. One of the db.telephony.common.jar files plays a role as well as a system//framework/lib file. Let me research this a bit and I'll get back to you on exactly what to edit. I've been developing on the Moto E LTE Surnia and the Moto E5 Play James a lot lately, so I tend to sometimes cross up device configs. There is a thread dedicated to this exact subject and it seems the simplest was to achieve GSM support on the more recent OS builds is to downgrade the radio firmware to a previous version. But again, I'll double check this.
Flashing the firmware package does not re-lock the bootloader. You must manually relock it should you want your device back in OEM locked state.
 
Last edited:

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
You're completely right. I recall now that apns-config.xml is not the only file needing editing. One of the db.telephony.common.jar files plays a role as well as a system//framework/lib file. Let me research this a bit and I'll get back to you on exactly what to edit. I've been developing on the Moto E LTE Surnia and the Moto E5 Play James a lot lately, so I tend to sometimes cross up device configs. There is a thread dedicated to this exact subject and it seems the simplest was to achieve GSM support on the more recent OS builds is to downgrade the radio firmware to a previous version. But again, I'll double check this.
Flashing the firmware package does not re-lock the bootloader. You must manually relock it should you want your device back in OEM locked state.

Ok Thanks For your Good Job Man , i just wanted to know if it was possible to re-lock the bootoader but not for my phone . Well Im Going To Leave The Phone as it is now but if there is some way to edit apn on new stock firmware maybe some magisk module or xposed app , would be nice , i just need oreo lineageos 15.1 in some certain future.
 

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
Ok Man I Upgraded M Device No Problems But No Way To Introduce My Custom Apn Settings I Really Need a Way I Been Looking around on Google and Nothing GravityBox Cant edit Apn Dont Know What To Do Just ...
 

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
#1 = I Flashed This Upgrade and i had to rollback downgrading to the original Stock , Why well No way to Add Custom Apn , Magisk Modules Wont work with the new kernel and if i flash older kernel with f2fs loopback bug patched WIFI wont work , So No Apn , No Magisk Modules , No Xposed . And Neither the F2fs Loopback bug Workaround works i used the last version . this new Stocks Are Not For Me but thanks anyway because now i have newer Bootloader.
 

MotoJunkie01

Senior Member
Apr 2, 2016
2,403
1,213
Corbin
Ok Thanks For your Good Job Man , i just wanted to know if it was possible to re-lock the bootoader but not for my phone . Well Im Going To Leave The Phone as it is now but if there is some way to edit apn on new stock firmware maybe some magisk module or xposed app , would be nice , i just need oreo lineageos 15.1 in some certain future.
To relock your bootloader, you can use either the WinDroid Toolkit or you can use the exact opposite command that you used to unlock it.

fastboot oem lock
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,287
#1 = I Flashed This Upgrade and i had to rollback downgrading to the original Stock , Why well No way to Add Custom Apn , Magisk Modules Wont work with the new kernel and if i flash older kernel with f2fs loopback bug patched WIFI wont work , So No Apn , No Magisk Modules , No Xposed . And Neither the F2fs Loopback bug Workaround works i used the last version . this new Stocks Are Not For Me but thanks anyway because now i have newer Bootloader.
The f2fs loopback bug workaround module works fine on the latest update. Flash it in twrp. Sometimes you have to flash it twice.
 

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
Thanks @madbat99 for the tip , now I need Someone Who Tells Me How To Add Customs Apn Settings Using This New Version Of Stock Android , I Really Like to Have Android Security Patches And Kernel With All The New Improvements
But Cant Find Any Way To Edit Apns On This Rom Anybody Knows ? this is sad..
 

MotoJunkie01

Senior Member
Apr 2, 2016
2,403
1,213
Corbin
Thanks @madbat99 for the tip , now I need Someone Who Tells Me How To Add Customs Apn Settings Using This New Version Of Stock Android , I Really Like to Have Android Security Patches And Kernel With All The New Improvements
But Cant Find Any Way To Edit Apns On This Rom Anybody Knows ? this is sad..
On my xt1766, I initially told you wrong. Sorry about that. I was referring to the apns-config.xml on another Moto device of mine. I used the MSL code on my xt1766 to manually set the APN to a GSM carrier. (in my case, AT&T). Network preferences and such can also be edited with your MSL, including LTE band priority and carrier aggregation settings. You can get your MSL by contacting your mobile provider and giving them your device info, MEID, etc. To enter into MSL programming mode (Data Settings Menu), just go to your dialer and enter ##3282#. You will be prompted for your six digit MSL by selecting the "Edit" option in any of the listed fields.
 

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
On my xt1766, I initially told you wrong. Sorry about that. I was referring to the apns-config.xml on another Moto device of mine. I used the MSL code on my xt1766 to manually set the APN to a GSM carrier. (in my case, AT&T). Network preferences and such can also be edited with your MSL, including LTE band priority and carrier aggregation settings. You can get your MSL by contacting your mobile provider and giving them your device info, MEID, etc. To enter into MSL programming mode (Data Settings Menu), just go to your dialer and enter ##3282#. You will be prompted for your six digit MSL by selecting the "Edit" option in any of the listed fields.

Ok There Is No Other Way To Get The Msl Code , Because i Don Really Know if "Viva" here in domican republic know this i dont think so , they dont now how to give me a msl code , is a new company
 

ozmage

Senior Member
Jun 28, 2017
161
45
35
Santo Domingo
On my xt1766, I initially told you wrong. Sorry about that. I was referring to the apns-config.xml on another Moto device of mine. I used the MSL code on my xt1766 to manually set the APN to a GSM carrier. (in my case, AT&T). Network preferences and such can also be edited with your MSL, including LTE band priority and carrier aggregation settings. You can get your MSL by contacting your mobile provider and giving them your device info, MEID, etc. To enter into MSL programming mode (Data Settings Menu), just go to your dialer and enter ##3282#. You will be prompted for your six digit MSL by selecting the "Edit" option in any of the listed fields.

##3282# Dont work for me
 

Attachments

  • Screenshot_20180728-130819.png
    Screenshot_20180728-130819.png
    63.8 KB · Views: 189

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    --- QUALCOMM ONLY ---
    Motorola Moto E (4th Gen) SPerry xt1766
    Stock Android 7.1.1 Factory Firmware
    Build No. NCQS26.69-64-10
    Blur_Version.26.231.8.sperry_sprint.sprint.en.US
    Restoration & Firmware Flashing Guide

    WARNING: by proceeding further, you are assuming full responsibility for the integrity and operability of your device. Although this firmware package has been fully tested on my own device, I am not responsible in the event something goes wrong. Follow the comprehensive instructions and things should go smoothly and without incident.

    Thanks & Credit:
    Once again, I owe credit and give an abundance of thanks to XDA member @ALI12 for so graciously providing this needed firmware package. His RSD Lite firmware thread for this build is here https://forum.xda-developers.com/mo...tock-rom-moto-e4-sprint-ncqs26-69-64-t3852464
    I would respectfully ask any members who use this firmware to thank @ALI12 on the above thread.

    CHANGELOG:
    This firmware update brings standard bug fixes and stability improvements, as well as security patches up to September 1, 2018. Please note that the radio firmware (baseband version) was not updated from the previous firmware build, and remains at version M8920_15000.280.06.58.05R. However, the radio firmware did receive some minor patches to improve cellular data handover whenever a WiFi connection loses internet access or becomes unstable. Patches were also added to update the PRL databases.

    SPECIFICATIONS:
    Device Name: Motorola Moto E (4th Gen)
    Compatibility: xt1766 SPerry (Qualcomm)
    Provider(s): Sprint, Boost Mobile, Virgin Mobile
    Android Version: 7.1.1 Nougat
    Build No. NCQS26.69-64-10
    System Version: 26.231.8.sperry_sprint.en.US
    Bootloader Version: moto-msm8920-BB.32
    Radio Version: M8920_15000.280.06.58.05R
    Kernel Version: 3.18.31-perf
    FSG Version: FSG-8953-11.22
    Build Date: August 28, 2018
    Security Patch Level: September 1, 2018
    Package Size: 1.55 GB

    APPLICABILITY:
    Flashing this firmware package via the instructions below will restore your device to the default stock factory configuration. Also, your device will be up to date with the latest firmware version. All files, media, etc., stored on your device will be erased, so please make a suitable backup of anything important prior to proceeding. Flashing this package will enable dm-verity (device mapping), force encryption of the /userdata partition, and will remove any modifications such as root binaries, BusyBox, Xposed Framework, etc. Also, if you have a custom recovery installed, such as TWRP, it will be replaced with the stock recovery. Upon reboot, your device will be fully capable of installing any future OTA update packages as well.

    INSTRUCTIONS:
    This guide assumes that you already have the most current version of Minimal ADB and Fastboot utilities installed on your PC or laptop, as well as the most current version of Motorola Device Manager (to ensure current USB device drivers are installed on your PC/laptop). It is also assumed that you have at least a rudimentary understanding of AP Fastboot Mode and executing fastboot commands. While this package may be installed using alternative methods such as mFastboot or RSD-Lite, this guide focuses on a standard fastboot command set. Also, it should be noted that I have only tested this package on a device with the bootloader in an unlocked state. While, in theory, a factory firmware package should flash to a device with a locked bootloader, I have not confirmed on this package.

    NOTE: Flashing this firmware package to an OEM unlocked device does not re-lock the bootloader. Also, contrary to popular belief, your bootloader does not need to be in a locked state in order to install an OTA update package. The state of the bootloader has no significance with respect to OTAs. As long as your device has been flashed/restored with a factory firmware package -- such as this one -- OTA updates will install properly.

    1. Download the firmware package from the below link and extract the contents of the archive to your ADB/Fastboot directory on your PC;
    2. Power off your device, then hold the Power + Volume Down buttons simultaneously for 7 - 8 seconds until AP Fastboot Mode appears on your device display;
    3. Connect your device and PC using the OEM supplied, or quality equivalent, micro USB to USB charge/sync cable;
    4. Open a command prompt window in the path of your ADB/Fastboot directory. Execute the following command:

    fastboot devices

    If properly connected, your command prompt window will return an alphanumeric string synonomous with your device serial number;
    5. Once a proper connection has been confirmed, execute the following commands, preferably in this order:

    fastboot oem fb_mode_set
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.img
    fastboot flash modem NON-HLOS.bin
    fastboot flash fsg fsg.mbn
    fastboot erase modemst1
    fastboot erase modemst2
    fastboot flash dsp adspso.bin
    fastboot flash logo logo.bin
    fastboot flash boot boot.img
    fastboot flash recovery recovery.img
    fastboot flash system system.img_sparsechunk.0
    fastboot flash system system.img_sparsechunk.1
    fastboot flash system system.img_sparsechunk.2
    fastboot flash system system.img_sparsechunk.3
    fastboot flash system system.img_sparsechunk.4
    fastboot flash oem oem.img_sparsechunk.0
    fastboot flash oem oem.img_sparsechunk.1
    fastboot erase userdata
    fastboot erase cache
    fastboot erase DDR
    fastboot oem fb_mode_clear

    Reboot your device by executing:

    fastboot reboot

    Upon reboot, your xt1766 should now be restored to stock factory condition and running on the latest firmware build version.

    DOWNLOAD LINKS:
    Android 7.1.1 -- NCQS26.69-64-10: https://drive.google.com/file/d/1H5V6ZUHWhSrBn1_8pHq8_qrwiXYga2YC/view?usp=drivesdk



    PREVIOUS FIRMWARE BUILDS:
    Android 7.1.1 -- NCQS26.69-64-8:
    https://drive.google.com/file/d/1CG9Bb2csn2dWLy1jfP0yimhVpMq-NDub/view?usp=drivesdk

    Android 7.1.1 -- NCQS26.69-64-5:
    https://drive.google.com/file/d/1ZoACEF5-lruTu4yhGknKjUqdXxGTf7kQ/view?usp=drivesdk
    3
    Installed a new update from Boost today and phone boots straight to recovery every time now. Backup before you install if you take the risk.
    *edit* I gotta scan those last few posts better before I start typing.
    Are you talking about twrp recovery? If so,
    This version of TWRP is not reading and clearing the bootloader control block (BCB). So, if you do a factory reset via Settings->Backup & Reset->Factory Data Reset, you'll be stuck in a TWRP bootloop.

    The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.

    To clear the BCB manually, issue this command in TWRP terminal:

    Code:
    dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M

    Or alternatively, just issue the following command from the bootloader:

    Code:
    fastboot erase misc
    3
    Sorry, I do not have phone right now... But do I have Moto G5 Plus, which I was doing some modification on persist because of same Radio off issue.

    Baseband version was: M8953_37.46.07.01R POTTER_NA_CUST (Yes, R and but Radio was off).
    I changed ownership of /persist/rfs and /persist/hlos_rfs, I read about this somewhere in a section of Moto G5 Plus.
    After changing ownership of these two folder and it's files inside persist. I reboot my phone and saw baseband:
    It was changed to M8953_37.46.07.01e POTTER_NA_CUST (Yes, e in small latter, still radio off, but this gives us some hope) :)...
    command I used for changing ownership on twrp;




    @ALI12

    Did you get the success? Please let us know.

    ---------- Post added at 11:53 PM ---------- Previous post was at 11:46 PM ----------




    You are right that I mentioned wrong one..

    And reason for sharing this information is, keep your fingers crossed.. this can be fixed.... I am just a biggner and can not help you guys... All seniors and very much experienced.....

    This info can give them hope....human looses hope after making Few unsuccessful as attempts..

    ---------- Post added at 11:54 PM ---------- Previous post was at 11:53 PM ----------




    You are right that I mentioned wrong one..

    And reason for sharing this information is, keep your fingers crossed.. this can be fixed.... I am just a biggner and can not help you guys... All seniors and very much experienced.....

    This info can give them hope....human looses hope after making Few unsuccessful attempts..
    So, you really have no idea. You can't link any info, so you're basing it on something someone said I assume? How do you actually know someone fixed it? They said so, and shared no details? Sounds like bull$#it to me.

    Trying to boost false hope with no info helps no one.
    3
    Likely because they locked the phones down to carrier more than before. Sprint obviously doesn't want their carrier branded devices to be used on other networks.
    I concur with you 100%. The Sprint compatible variants of Motorola smartphones have a very lengthy history of being network locked and carrier restricted. Back in the days of the Surnia Moto E LTE 2015, the xt1526 Sprint variant shipped with encryption based network restrictions, whereas the /hob, /dhob and /pds partitions were embedded with code to effectually disable domestic GSM functionality. Of course, these partitions were protected read only by the bootloader.
    Nowadays, Sprint and its subsidiaries appear to be taking a direct firmware approach to carrier locking their devices, and restricting GSM functionality by way of the stock Android OS itself. When the providers learn of exploits (e.g. that GSM functionality is possible by using a custom ROM), OTA updates are rolled out to patch the loopholes. Such is the case here with the xt1766. However, I'm a but puzzled by the latest OTA restricting GSM support for international owners of the xt1766, as it has always been Sprint's policy to allow UICC unlocking of its devices for international GSM usage. It appears that the latest OTA included code to patch domestic GSM functionality, but that the patch inadvertently disabled international GSM support.
    I've been trying for months to get access to Motorola Mobility's mobile provider manifests, which contain source code and information specific to carrier branded variants of Motorola devices. Unfortunately, Motorola's office of general counsel now considers these manifests "privileged work product information." As such, this information is deemed classified and exempt from open records inspection laws.
    2
    Update: while getting the updated firmware package together, and testing on my own device, I believe I've figured out (fingers crossed) the radio bug with the latest OTA update. If so, my updated firmware package should fix any issues with the broken cell radio. I'll keep the thread updated with progress. Some more testing is necessary, but things are looking up.