FORUMS
Remove All Ads from XDA

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

2,403 posts
Thanks Meter: 1,203
 
By MotoJunkie01, Account currently disabled on 24th July 2018, 06:29 PM
Post Reply Email Thread
--- 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/mot...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/1H5V...w?usp=drivesdk



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

Android 7.1.1 -- NCQS26.69-64-5:
https://drive.google.com/file/d/1ZoA...w?usp=drivesdk
The Following 5 Users Say Thank You to MotoJunkie01 For This Useful Post: [ View ] Gift MotoJunkie01 Ad-Free
24th July 2018, 10:37 PM |#2  
Senior Member
Flag Santo Domingo
Thanks Meter: 18
 
More
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.
24th July 2018, 10:58 PM |#3  
OP Account currently disabled
Flag Corbin
Thanks Meter: 1,203
 
Donate to Me
More
Quote:
Originally Posted by ozmage

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.
25th July 2018, 12:01 AM |#4  
Senior Member
Flag Santo Domingo
Thanks Meter: 18
 
More
Quote:
Originally Posted by MotoJunkie01

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.
25th July 2018, 12:48 AM |#5  
OP Account currently disabled
Flag Corbin
Thanks Meter: 1,203
 
Donate to Me
More
Quote:
Originally Posted by ozmage

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.
25th July 2018, 01:50 AM |#6  
Senior Member
Flag Santo Domingo
Thanks Meter: 18
 
More
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.
25th July 2018, 02:13 AM |#7  
OP Account currently disabled
Flag Corbin
Thanks Meter: 1,203
 
Donate to Me
More
Quote:
Originally Posted by ozmage

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.
25th July 2018, 08:18 AM |#8  
Senior Member
Flag Santo Domingo
Thanks Meter: 18
 
More
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.
25th July 2018, 08:27 AM |#9  
OP Account currently disabled
Flag Corbin
Thanks Meter: 1,203
 
Donate to Me
More
Quote:
Originally Posted by ozmage

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.
25th July 2018, 10:09 AM |#10  
Senior Member
Flag Santo Domingo
Thanks Meter: 18
 
More
Quote:
Originally Posted by MotoJunkie01

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.
25th July 2018, 04:07 PM |#11  
Senior Member
Flag Santo Domingo
Thanks Meter: 18
 
More
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 ...
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes