How to Flash a T Mobile Firmware Version Moto E4

OVERVIEW:
This guide provides factory firmware for both the MetroPCS and T-Mobile branded variants of the Moto E4 Perry (xt1765). While these two packages appear to be similar and multi-compatible, I do not own the xt1765 and cannot confirm this. So, to be condom, utilize only the firmware package for your branded carrier. This guide can be used to repair a device which is buggy, unstable, or stuck in a kicking loop. Likewise, device owners wishing to restore their device to an unmodified, stock factory state volition too find this guide beneficial. Installing this firmware will remove whatever custom mods from your device, such equally root binaries, BusyBox binaries, Xposed framework, etc. Also, force encryption and verified boot (dm-verity/avb) volition be enabled. If you have TWRP custom recovery installed, it will exist replaced past the stock recovery image.

DISCLAIMER:

You are using this guide and flashing firmware to your device solely at your own risk. While these firmwares take been tested and confirmed to piece of work on their respective variants, past proceeding further, y’all are absolving me of any liability or responsibility in the event you brick your device or otherwise render it inoperable. Follow the simple instructions carefully and things should go smoothly.

SPECIFICATIONS:
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•MetroPCS Moto E4 (xt1765) Perry
•Android Version: seven.1.1 Nougat

•Build No. NCQS26.69-64-iii
•System Version: 26.261.9.perry_metropcs.en.Us
•Radio Version: M8917TMO_18.08.04.18R
•Security Patch Level: March 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: March 16, 2018
•Firmware Parcel Size: 1.36 GB
•Download Link:
https://drive.google.com/file/d/17sJS8VpxSAHupqiqJQQb4wa1jHIP61uT/view?usp=drivesdk

•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•T-Mobile Moto E4 (xt1765) Perry
•Android Version: 7.1.one Nougat
•Build No. NCQS26.69-64-6
•System Version: 26.271.7.perry_tmo.tmo.en.US
•Radio Version: M8917TMO_18.08.04.eighteen.01R
•Security Patch Level: May 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Appointment: May 2, 2018
•Firmware Package Size: ane.33 GB
•Download Link:
https://drive.google.com/file/d/1C21fgdBVn6hhPtAo5yult-PdB6DSr4HS/view?usp=drivesdk

•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

REQUIREMENTS:
This guide assumes that you have the latest version of the Minimal ADB & Fastboot utilities installed on your PC or laptop. If you do non, you can download the latest version, v1.4.3, from this MediaFire link:
http://www.mediafire.com/file/ccnnv843a20tqbn/minimal_adb_fastboot_v1.4.3.zip
It is also a good thought to have at to the lowest degree a rudimentary agreement of fastboot command line execution. At that place are some excellent guides here on XDA which outline the subjects of fastboot mode & fastboot commands.

In addition, to ensure that up-to-date USB device drivers are installed on your PC, download & install the latest Motorola Device Managing director. You can become the latest version directly from this Motorola support link:
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222

NOTE:
Considering these are manufactory firmware packages, in theory, xt1765 owners should be able to wink these packages, using the below instructions, to devices with a locked bootloader. Please note, still, that these firmwares were leaked past the manufacturer and may or may not be digitally signed past the OEM. In sum, I cannot confirm whether these firmwares will flash to a locked bootloader device. I tin can only confirm that the firmware volition install normally on a device with an unlocked bootloader. As confirmation becomes bachelor from other members in this regard, I will add the info to this thread.

On a second note, flashing this manufacturing plant firmware does non re-lock an already unlocked bootloader. Besides, contrary to popular misbelief, re-locking your bootloader IS Not required in order for your device to be able to install OTA update packages. To enable your device to install OTA updates, you need but install the firmware package for your variant using the beneath instructions.

Warning: The below instructions include a command for wiping your /userdata partition (fastboot erase userdata) which volition effectively wipe all of your saved files, photos, videos, app information and other media. This is recommended for a clean install of the firmware, and to ensure optimal results. However, if you are stuck in a kick loop, for example, and take important files saved to internal storage that you want to try and relieve, simply skip over the “fastboot erase userdata” command and give it a try.

INSTRUCTIONS:
• 1. Download the firmware package for your branded carrier on your PC or laptop. Extract the contents of the package to your ADB/Fastboot directory;
• 2. Boot your device into fastboot way and connect your device to your PC with the OEM or a quality equivalent micro USB to USB sync cable;
• 3. Open a command window in the path of your ADB/Fastboot directory and execute:

fastboot devices

If your device and PC are properly connected, the control window will return an alphanumeric value synonymous of your device series number;
• iv. Once a proper connection has been established, 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 wink dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot wink organization arrangement.img_sparsechunk.0
fastboot flash system organisation.img_sparsechunk.1
fastboot flash organization arrangement.img_sparsechunk.ii
fastboot wink system system.img_sparsechunk.3
fastboot flash system arrangement.img_sparsechunk.iv
fastboot flash oem oem.img
fastboot erase userdata

fastboot erase enshroud

fastboot erase DDR
fastboot oem fb_mode_clear

Done. Now execute:

fastboot reboot

Upon reboot, your device should be restored to unmodified stock status, and your device will be capable of installing pending or futurity OTA update packages.

Thanks for posting this! Looks very comprehensive and nOObproof…. I’thou going to endeavor this out in the adjacent few days and I will report back if I had any trouble following the instructions and let your know if I experience anything needs to be antiseptic. I don’t foresee having any bug with this though. I appreciate you lot and your hard work to put this together

No trouble. I’ve been reading a lot of posts of members needing more up-to-engagement xt1765 stock firmware, so I promise it helps some members. These are the same instructions and structural format that I utilize on all of my Moto/Lenovo firmware threads. The order of the command lines are prepare out exactly the same as those used in certified Motorola/Lenovo service centers. If you follow the instructions to the letter, there is no dubiousness that you’ll have your device fully restored to stock mill condition.

Shiiiiiit I didn’t think about that I have an update I’m going to try to do information technology if it doesn’t work guess I’ll redo the full procedure all over again….. By the way I pmd you

EDIT: 69-64-vi updated no problem And immediately offered me 69-64-9 so maybe these updates aren’t big enough to worry nigh twrp instead of stock recovery? Only time will tell I guess

To simplify things, just continue installing OTAs until you lot are on the current build. So, reinstall TWRP. Yous shouldn’t have to redo the whole matter as long as you haven’t mounted organization as r/w in TWRP. And every bit long as you haven’t flashed Magisk or SuperSU for root. Just reboot into fastboot and flash the stock recovery and OTAs should be fine.

so i know im a hurting in the donkey but i followed this guide with no issues and updated fully before installing twrp and root and and then couldnt install xposed and ran into a bootloop and then decided to become nuclear and start over. My just issue now is after fully following this guide again my OTA updates are declining in stock recovery and when i reboot i get tons of tmobile and moto app FC problems and it says im fully updated even though i started on 69-64-3 and information technology failed in stock recovery information technology yet says im on 69-64-6 and ive been on 69-64-9 before and then not but do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my bug? im having a lot of problems with noverity flashing correct and getting the newest twrp to wink instead of only temp kick besides and i feel these issues are all cnnected somehow. I might get dorsum to RR if possible because i was able to go my phone the way i wanted on there for the most office im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or annihilation considering i am retrying this guide once more and see how it goes and didnt remember until after the fact to mail service this

Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those volition fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs commonly.
If that particular problem persists, file corruption within the firmware package could be the culprit. Endeavour downloading the firmware again (delete the other from your PC) and start over from scratch.

Ok thanks. I volition endeavour redownloading if it persists but is there any log or anything that would help out in identifying the problem if it all the same persists afterwards a redownloading of the firmware? It’south annoying that stock recovery says error! With no lawmaking to aid identify the issue

When stock recovery says ERROR during installation of an OTA, the problem is with the checksums. In other words, the OTA installer is telling stock recovery that you lot are non running an unmodified stock setup. You can get an mistake like that from but mounting /system or /oem as r/w. The installer checks your /kick, /recovery, /organization and /oem partitions to make certain they are untouched, unmodified stock.

Okay and then I redid this and the updates are sticking like yous said I must take changed something and made it non-stock…. And so I do not need the RSD Light every bit of yet simply I did download information technology. Looking into it it seems that I may use information technology to root my device when I get to that indicate? For now I’grand simply setting everything upwards the way I like information technology and fully intalling stock updates before I go into TWRP and rooting. The goal is a upward to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it’s due to my crappy understanding of selinux permissions, encryption and dm verity…. The all-time thing virtually struggling to install stuff like this is it gives you an opportunity to acquire. In the past I’ve been able to follow guides and everything worked as stated then I had no demand to get technical and delve into some of the things I’ve needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?

That’southward good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. In one case you lot are on the latest stock build, if you could brand a TWRP backup of your organization image and boot image and upload them, I could use the images to cook up an up-to-engagement stock ROM for the xt1765.

Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will nevertheless work? Basically is the stock recovery needed or tin can I wink TWRP before I make the backup

so system and boot only or organization, system image, and boot? making one now with both systems and 1 with simply normal system since im not certain which you need and dont want to give you to much **** to sift through. also does information need to be decrypted for this to be helpful to y’all? sorry dont know much well-nigh it merely am willing to assist lol

System epitome and kick backup with TWRP. Encryption of information isn’t relevant to the backups. Whether y’all boot into TWRP or flash TWRP ….either will work

As well verify checksums (MD5, SHA-1, etc) when offered. Fastest fashion to validate large file integrity. As a matter of practice I never wink critical partitions sans checksum validation.

Excellent point. A corrupt wink to a critical partition can equal lights out — the proverbial difficult brick.