Database Info

[Droid Turbo XT1254] Bootloader & Radio Packages (+Unlocked warning removal)

This will update your device to the latest radio/bootloader images available. Unlocked bootloaders will remain unlocked.
This will remove your ability to use moforoot if you're upgrading from a 4.4 bootloader, so only use this if you're unlocked using SunShine.
I will update this thread as new OTAs come out.
Instructions for using fastboot packages:
Code:
adb reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
Or if you have TWRP installed, you can use the flashable TWRP packages instead.
5.1 (SU4TL-49)
WARNING:
The SU4TL-49 bootloader fixes the exploit used for the SunShine unlock.
However, unlocked bootloaders will remain unlocked.
Fastboot package (Mirror)
SHA1 sum: a297a5fd84f906cdfacf4efb8c656babbfe2452f
Flashable TWRP package (Mirror)
SHA1 sum: a85d11383d2543ae527846df0156886b51021dae
5.1 (SU4TL-44)
Fastboot package (Mirror)
SHA1 sum: a89e128f9eb518091f3370d3f2c83ab27f759732
Flashable TWRP package (Mirror)
SHA1 sum: 7b2d632aabdf8718650644bf74fb2824c31907c1
"Unlocked" warning removal
Flashable TWRP package (Mirror)
SHA1 sum: cc30ea56d134ef4585b7c2600ffff50955b10c07
Also flashable using fastboot by using
Code:
fastboot flash logo logo.bin

Thank you good sir!

firstEncounter said:
This will update your device to the latest radio/bootloader images available. Unlocked bootloaders will remain unlocked.
This will remove your ability to use moforoot if you're upgrading from a 4.4 bootloader, so only use this if you're unlocked using SunShine.
I will update this thread as new OTAs come out.
Instructions for using fastboot packages:
Code:
adb shell sync && adb reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
Or if you have TWRP installed, you can use the flashable TWRP packages instead.
5.1 (SU4TL-44)
Fastboot package
SHA1 sum: a89e128f9eb518091f3370d3f2c83ab27f759732
Flashable TWRP package
SHA1 sum: 7b2d632aabdf8718650644bf74fb2824c31907c1
"Unlocked" warning removal
Flashable TWRP package
SHA1 sum: cc30ea56d134ef4585b7c2600ffff50955b10c07
Also flashable using fastboot by using
Code:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
This is only for if you werent on SU4TL-44, right?

Marky__Mark said:
This is only for if you werent on SU4TL-44, right?
Click to expand...
Click to collapse
Right now it's only useful for mofo users who updated to 5.1, since their BL was left on 4.4. If you updated using the SU4TL-44 OTA or factory image, there's no need to use this, since everything is already up to date.
In the future, custom ROM users will likely need to use these images to stay up to date on BL/radio as they're released.

firstEncounter said:
Right now it's only useful for mofo users who updated to 5.1, since their BL was left on 4.4. If you updated using the SU4TL-44 OTA or factory image, there's no need to use this, since everything is already up to date.
In the future, custom ROM users will likely need to use these images to stay up to date on BL/radio as they're released.
Click to expand...
Click to collapse
Thanks

What would be nice to have is the availability of a bone-stock 5.1 flashable ROM. Once we upgrade to the new BL and radios, we won't be able to flash the stock IMGs (as far as i know) you have listed here as MOFO will no longer work. You can always FXZ but it's a pain. Thanks!
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-5-1-rooted-images-t3152563

I used cf mofed 1.6 lollypop ROM and I unlocked via sunshine and now I'm running with RR ROM , so I also need to update or flash these packages ?? SU4TL-44 ??

GeoFX said:
What would be nice to have is the availability of a bone-stock 5.1 flashable ROM. Once we upgrade to the new BL and radios, we won't be able to flash the stock IMGs (as far as i know) you have listed here as MOFO will no longer work. You can always FXZ but it's a pain. Thanks!
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-5-1-rooted-images-t3152563
Click to expand...
Click to collapse
Once the bootloader is unlocked, you'll just be able to flash the system images using
Code:
fastboot flash system xt1254-5.1-stock-system-v3.img
You'll also want to flash the boot.img and wipe data/cache if coming from a different ROM. Then you'll be able to flash your own SuperSU/Xposed, etc zips over it if desired.
I probably won't be packaging them into a flashable zip due to the file size. I'd just recommend making a backup of the stock ROM in TWRP.
aneeshmbabu said:
I used cf mofed 1.6 lollypop ROM and I unlocked via sunshine and now I'm running with RR ROM , so I also need to update or flash these packages ?? SU4TL-44 ??
Click to expand...
Click to collapse
It's not required, only if you want to stay up to date on radio/BL.

Thanks, flashed the zip that fixed the bootloader warning, on the razrm we did very similar, looks like I'm going to have to make a few images.
Sent from my XT1254 using XDA Free mobile app

firstEncounter said:
This will update your device to the latest radio/bootloader images available. Unlocked bootloaders will remain unlocked.
This will remove your ability to use moforoot if you're upgrading from a 4.4 bootloader, so only use this if you're unlocked using SunShine.
I will update this thread as new OTAs come out.
Instructions for using fastboot packages:
Code:
adb shell sync && adb reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
Or if you have TWRP installed, you can use the flashable TWRP packages instead.
5.1 (SU4TL-44)
Fastboot package
SHA1 sum: a89e128f9eb518091f3370d3f2c83ab27f759732
Flashable TWRP package
SHA1 sum: 7b2d632aabdf8718650644bf74fb2824c31907c1
"Unlocked" warning removal
Flashable TWRP package
SHA1 sum: cc30ea56d134ef4585b7c2600ffff50955b10c07
Also flashable using fastboot by using
Code:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
Hey @firstEncounter thanks for your work! I used your v3 rooted system image via mofo in order to get sunshine to work, now I'm unlocked! Just to be clear after I take these steps will I be on official stock 5.1? I used your steps to pre flash those things prior to flashing 5.1 with mofo as you had said it would allow us to downgrade to kk. Is it necessary to go back to kk in your opinion? Any benefit? Basically I'm asking if I should keep the current setup or do this flash? Thanks in advance.

bigguy0691 said:
Hey @firstEncounter thanks for your work! I used your v3 rooted system image via mofo in order to get sunshine to work, now I'm unlocked! Just to be clear after I take these steps will I be on official stock 5.1? I used your steps to pre flash those things prior to flashing 5.1 with mofo as you had said it would allow us to downgrade to kk. Is it necessary to go back to kk in your opinion? Any benefit? Basically I'm asking if I should keep the current setup or do this flash? Thanks in advance.
Click to expand...
Click to collapse
After these steps you'll be running the latest bootloader, it won't affect the ROM you're running. There will likely be no perceivable changes other than the version number in the bootloader menu, but there's also no reason to stay on the 4.4 bootloader.
With an unlocked bootloader, downgrading to KK should be possible (haven't tried it), though at this point I don't see why there would be any reason to do so.

I'm looking in about phone, but I can't tell how I'd know that I'm on the latest bootloader and radios.

Droid1019 said:
I'm looking in about phone, but I can't tell how I'd know that I'm on the latest bootloader and radios.
Click to expand...
Click to collapse
In the bootloader, you'll see version 70.86 for BL and 11.05.16.02R for Baseband.

Assuming I can use the "unlocked warning removal" if I unlocked from 5.1 and did not come from a mofo root device?

m4rk0358 said:
Assuming I can use the "unlocked warning removal" if I unlocked from 5.1 and did not come from a mofo root device?
Click to expand...
Click to collapse
Yes.

Just checking before I flash: will the unlocked warning remover set it back to the same M logo it was before, or is this a different boot logo?
Thanks!

Coronado is dead said:
Just checking before I flash: will the unlocked warning remover set it back to the same M logo it was before, or is this a different boot logo?
Thanks!
Click to expand...
Click to collapse
Same logo, just no unlocked warning.

Came from Mofo 5.1 to Sunshine and running ComputerFreak's Unlocked 1.2 rom. Updated Booloader/baseband and removed bootloader warning files both flashed in TWRP with no problems. Thank you!

Any bugs with the twrp flashable bootloader unlock warning zip file?
Sent from my XT1254 using Tapatalk

It worked fine.
Sent from my DROID Turbo using XDA Free mobile app

How do I update rooted shield tablet to marshmallow?

OK, so I have a shield tablet that is running a rooted stock android version 5.1.1 and I want to update it too marshmallow and retain root. I have TWRP as my recovery. What's the easiest way to update? I found a thread for updating to marshmallow and it said it had the auto update file removed (which is good) but the downloadable files were removed from the thread by the OP... I should mention that this tablet is the newer recall replacement tablet that I'm trying to update, and that I still have the old recalled tablet with the auto update file removed so it never got killed. I'm not updating the old one though, just the new one.

You have to take care, not to overwrite the recovery partition. At least for the K1 there is an MM stock ROM on the official website. The version for linux simply contains partition images and a script, which fastboot flashes those. Commenting out the line which flashes the recovery would do the trick.
I'm not sure though if there is a similar ROM for the original.
Ah... no, with a locked bootloader it's slightly more complicated, since a 5.x twrp won't start on with a 6.0 staging blob.
Ok. Assume you've got the partition images. You have to (fastboot) flash everything but the blob and recovery first. Then boot into TWRP (the rom does not boot now) and flash your favorite SU tool. Then fastboot flash the blob. Now the rom should boot and give you root access. Finally update Twrp to 3.x.

njhuiz said:
You have to take care, not to overwrite the recovery partition. At least for the K1 there is an MM stock ROM on the official website. The version for linux simply contains partition images and a script, which fastboot flashes those. Commenting out the line which flashes the recovery would do the trick.
I'm not sure though if there is a similar ROM for the original.
Ah... no, with a locked bootloader it's slightly more complicated, since a 5.x twrp won't start on with a 6.0 staging blob.
Ok. Assume you've got the partition images. You have to (fastboot) flash everything but the blob and recovery first. Then boot into TWRP (the rom does not boot now) and flash your favorite SU tool. Then fastboot flash the blob. Now the rom should boot and give you root access. Finally update Twrp to 3.x.
Click to expand...
Click to collapse
Oh OK, thanks. I think I'll just wait. I'd rather flash a community stock/rooted rom. I don't want to flash an official ROM and have to re-root and flash recovery and all that... That's all just too much work right now just for marshmallow lol. My 5.1.1 is working fantastic so I'll just leave it for now. I'm curious why its so complicated now though with MM? I don't ever remember any previous build jumps requiring so much work to update to... My nexus 5 wasn't difficult at all. I just downloaded the full rom zip (MM Cataclysm cause I was on Lollipop Cataclysm), booted into TWRP, dirty flashed the zip, and it was good to go. I'm looking for THAT kind of update for my shield tablet.

If you unlock your bootloader (which is recomended for using custom roms), then getting root is simple, since you can fastboot flash any partition image.
Independend of your currently installed rom you can always get root by
1. (fastboot) flash the correct (2.7.x for Android 5.x, 3.x for Android 6.x) TWRP recovery
2. boot into TWRP an install a current SuperSU zip.
On the shield tablet you need to flash a new staging blob for MM in any case.

Been awhile
njhuiz said:
If you unlock your bootloader (which is recomended for using custom roms), then getting root is simple, since you can fastboot flash any partition image.
Independend of your currently installed rom you can always get root by
1. (fastboot) flash the correct (2.7.x for Android 5.x, 3.x for Android 6.x) TWRP recovery
2. boot into TWRP an install a current SuperSU zip.
On the shield tablet you need to flash a new staging blob for MM in any case.
Click to expand...
Click to collapse
I am attempting to update to marshmallow as well so i can install kali nethunter 3. but i am unfamiliar with rooting i havent done it since 2010. where would i acquire these files that i need to flash to the shield?

[CAPTURED OTA] September security patch (NPJS25.93-14-10)

#WeirdMoto
Motorola started rolling out September security patch which, you know, fixes Blueborn vulnerability. But instead of starting in India or other Moto's favorite country, they stated rolling it out in Latin America!
Changes:
-September security patch
-Bug fixes
Here you go! https://mega.nz/#!OU10kJAD!V2eW4QoXuGjzlLlct4NG-eQ5NvLru9em0aG8_CrSA9o (sorry because of Mega lol)

Thanks,can someone upload a twrp backup?

Can I flash if my device is rooted and I have TWRP?

ElGranLagarto said:
Can I flash if my device is rooted and I have TWRP?
Click to expand...
Click to collapse
No

ElGranLagarto said:
Can I flash if my device is rooted and I have TWRP?
Click to expand...
Click to collapse
Unlikely - the OTA would possibly fail and also leave you in a TWRP soft bootloop unless you booted to bootloader and then selected 'Start' to boot to system.
As this OTA will only flash on NPJS25.93-14-8 systems (looking at the updater script), the easiest way would be to use the NPJS25.93-14-8 stock ROM to revert to a fully stock device. Of course, this will remove root and TWRP on your device, but OTAs require a clean, unmodified device to work from.
Assuming you are currently on NPJS25.93-14-8 and were fully updated before flashing TWRP and rooting, you may be able to use the following flashing commands with the fastboot stock ROM to revert to stock without affecting your data. These commands are edited assuming your GPT and bootloader are the same patch level as NPJS25.93-14-8. As always, back up your data in case you need to factory reset, and also this depends on your device being formally and fully updated to NPJS25.93-14-8 previously, if not formally updated (including bootloader to B1:06), you may run into issues including a hard brick. If you are not sure, ignore the following flashing commands and fully flash the NPJS25.93-14-8 stock ROM as per in the linked post. Or wait for the TWRP flashable of the NPJS25.93-14-10 system ROM (which only flashes the system side of the build).
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase cache
fastboot reboot
The stock ROM for the NPJS25.93-14-8 build is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
A formally updated system to NPJS25.93-14-8 should include:
Bootloader version at B1:06.
Modem version ending in 62.01R.
Security patch at 1 June 2017.
After this, you should be able to update to NPJS25.93-14-10 via OTA. Needless to say, after you update via OTA, it therefore becomes risky to flash the June 2017 stock ROM or any older ROMs. As we've seen previously, downgrading and then attempting to update via OTA runs a high risk of hard bricking, and it may be the case that the June 2017 blankflash we have no longer works once updated to September 2017. Be careful. If you need to revert back to stock after flashing the September 2017 OTA, wait for the NPJS25.93-14-10 stock ROM.
EDIT - I saw from your previous posts asking about the NPJ25.93-14-8.1 update. If you've updated from NPJ25.93-14 to NPJS25.93-14-8.1, you likely won't be able to flash this update anyway as the expected build is different to what the NPJS25.93-14-10 update is expecting.
For NPJ25.93-14-8.1:
Code:
Package expects build thumbprint of 7.0/NPJ25.93-14-8.1/2:user/release-keys or 7.0/NPJ25.93-14/16:user/release-keys
For NPJS25.93-14-10:
Code:
Package expects build thumbprint of 7.0/NPJS25.93-14-10/10:user/release-keys or 7.0/NPJS25.93-14-8/8:user/release-keys

Successfully installed in my XT1641 with NPJS25.93-14-8. Thanks for capture and upload it.

Hallo, my phone (XT1643) isn't rooted and is NPJS25.93-14-8 running. Is it possible to put the updatefile into the internal storrage and flash it with orig. Motorola Recovery?

How can apply this OTA
How can apply this OTa patch to my Moto g4 plus ...and now my build number is NPJS25.93-14-8 hope it works fine after update this OTA. And let me know how I can apply this OTA

Marv42 said:
Hallo, my phone (XT1643) isn't rooted and is NPJS25.93-14-8 running. Is it possible to put the updatefile into the internal storrage and flash it with orig. Motorola Recovery?
Click to expand...
Click to collapse
Niket03 said:
How can apply this OTa patch to my Moto g4 plus ...and now my build number is NPJS25.93-14-8 hope it works fine after update this OTA. And let me know how I can apply this OTA
Click to expand...
Click to collapse
Similar steps should apply to you both - verify that you have NPJS25.93-14-8 fully updated on your device (e.g. bootloader is version B1:06) and everything is stock and not modified - so no TWRP, root, or custom logo.bin for example. Your recovery should also be the same version that came with the NPJS25.93-14-8 stock ROM/OTA update. Having an unlocked bootloader is not a problem, though if it is unlocked, you should be seeing the unlocked bootloader warning when you boot (from a stock logo.bin).
1)Download the OTA update to your device, likely it'll be in the Downloads folder.
2)Follow these instructions to get to the stock recovery:https://forum.xda-developers.com/showpost.php?p=72981796&postcount=58
3)Once in the stock recovery, select the 'Apply update from SD card' command with the volume keys, press power to use the command.
4)Navigate to your Download folder and find the update.
5)Press power whilst the update is selected to install.
5a)If there's an issue with mounting internal memory, you may try the 'Mount /system' command and attempt to re-select your update.
6)Once the update is finished, you may wish to 'Wipe cache' from the recovery menu. You do not have to factory reset.
7)Once done, you can choose to reboot.
If you choose, you can wait for the OTA update to arrive, which should automate the process for you.
As always, once you've updated, it becomes very risky to downgrade. I'd suggest not to downgrade from the September 2017 stock update if you can (with an older stock ROM), or if you really want to, do not update via OTA. Use an updated stock ROM (Sept 2017 fastboot ROM, which currently we don't have yet) to update if you've downgraded.

Thanks! Applied successfully on my Moto G4 XT1624. Working great as always.

Firmware
Firmware Patch -10
rsdsecure-cloud.motorola.com/download/ATHENE_NPJS25.93-14-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Any changes !!!!! ... It says bug fixes so ......

Updated via OTA in India.

well I am rooted with magisk and custom kernel installed. and I got OTA for updating it, so should I update it via OTA or flash it through fastboot?

Fastboot

siddhesh9146 said:
well I am rooted with magisk and custom kernel installed. and I got OTA for updating it, so should I update it via OTA or flash it through fastboot?
Click to expand...
Click to collapse
You need full stock setup for flashing via an OTA, else it'll fail — that includes recovery, kernel and the ROM. In addition, you can update only a full stock ROM through fastboot, not an OTA.

zeomal said:
You need full stock setup for flashing via an OTA, else it'll fail — that includes recovery, kernel and the ROM. In addition, you can update only a full stock ROM through fastboot, not an OTA.
Click to expand...
Click to collapse
I already flashed it from fastboot; thanks for your help!

siddhesh9146 said:
I already flashed it from fastboot; thanks for your help!
Click to expand...
Click to collapse
Siddesh how to update please tell me
---------- Post added at 11:19 AM ---------- Previous post was at 11:19 AM ----------
siddhesh9146 said:
I already flashed it from fastboot; thanks for your help!
Click to expand...
Click to collapse
Send me d link of stock rom of September patch

usha55 said:
Siddesh how to update please tell me
---------- Post added at 11:19 AM ---------- Previous post was at 11:19 AM ----------
Send me d link of stock rom of September patch
Click to expand...
Click to collapse
Link for the September 2017 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
If you wish to update and try to save your data (provided you were on an earlier stock Motorola build), have a look at the flashing commands in this post: https://forum.xda-developers.com/showpost.php?p=73970028&postcount=251 Else, you'll have to use the flashing commands in the main thread, which will wipe your data, so back up as required. You do not have to relock your bootloader if you do not wish to.

anyone tell me please if i lock oem now can i get normal updates from only im fed up of doing this fastboot,,and 1 more qstion if i lock my bootloader/oem can i unlock it again
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
why because im a hard brick survivor ,now if i unlock oem/bootloader i can update my phone normally from system updates
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
anuone reply me guys

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8

Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!

Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.

Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?

Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.

annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?

hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?

Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:

Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.

How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol

Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)

Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?

GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...

annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse

I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing

Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?

[XT1575][FIRMWARE][OFFICIAL] Moto X Pure Factory Firmware Nougat NPH25.200-22

I take no credit for this, thank the Motorola-Firmware-Team on Android File Host, and you can follow any leaked firmware on their Twitter feed.
I no longer have a Moto X Pure Edition, so I can't personally vouch for this firmware, but it seems like it is a totally legit full factory firmware image of Nougat NPH25.200-22 for flashing in fastboot.
This is the "official" full factory image of Nougat NPH25.200-22 and NOT the OTA file. It can be used for a clean flash and to relock the bootloader which is recommended to pass SafetyNet API checks if you are planning on staying stock and not rooting.
Flashfile.xml shows: version="clark_retus-user 7.0 NPH25.200-22 21 release-keysM8992_1255331.29.01.88.09R", MD5 matches, and all dates are correct.
This is ONLY for the Moto X Pure Edition, Retail US (RETUS) variant. I have no information on any other firmware or device.
Tested and verified as official Nougat factory ROM image by @Andromendous
This image is NOT flashable in TWRP, like all factory images it is flashed with fastboot in the bootloader... How to flash:
Code:
fastboot oem lock begin (if wanting to re-lock bootloader, othewise use `fastboot oem fb_mode_set`)
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock (only if you used `fastboot oem lock begin`, otherwise end with `fastboot oem fb_mode_clear`)
fastboot reboot
See https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 for detailed instructions
Downloads
Original source: https://androidfilehost.com/?fid=889964283620765304
Google Drive mirror: [removed]

@acejavelin: Since you have been one of the guru's on this phone, can this file be flashed in fastboot directly if I am on stock MM android December update rooted with Magisk and TWRP installed? I just want to make sure that when I am ready to take the plunge, I can take the minimal work procedure since I factory wipe after all major updates anyway.

Does this mean people who haven't received 7.0 OTA can flash this ROM and get Nougat without any complications such as corrupted bootloader and stuff? Also read multiple times that downgrading to 6.0 and again upgrading to 7.0 via OTA corrupts the bootloader leading to hard brick (which is now solver using external SD), will flashing this would solve this too?

Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.

acejavelin said:
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
Click to expand...
Click to collapse
Great! I plan on holding on to this phone for about another 6 months or so and might as well get the update. Will probably go over to stock nougat in December. Custom ROMs just always seem to have at best some minor issue(s) that prevents me from sticking with them.

Dude Ace you are the f-ing man. Thanks for the find.

I flashed it manually while on Hashbangs LOS rom. I was stuck on 6.0 modem and tried to just flash the modem, which made me lose sim service. I then flashed the entire imagine manually and booted just fine.
Now I'm back to LOS with 7.0 modem and so far so good. Hashbang is doing a great job, he's already cleaned multiple bugs just today.

i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.

schneid said:
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
Click to expand...
Click to collapse
It's a factory image... Have to flash each piece manually with fastboot, this is not a flashable TWRP or other recovery image

So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.

andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
We don't know that for sure... NPH25.200-22 is what has been rolling out to Sprint, T-Mobile, and AT&T devices, but it seems that Verizon users are getting NPH25.200-23 according to one verified (via screen shot) report on Lenovo's official forum.
The issue is we know the Moto OTA server keeps track of what device get's what version, if you flash this it won't know you have it so if a future OTA update comes out, you might be offered it via push and will have to wait until it's available by pull.

andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
Yes. There's a huge difference. With this you wont brick your phone.

Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?

CLETjB said:
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
Click to expand...
Click to collapse
Yes, you can relock... unless you have already applied NPH25.200-23, otherwise you should be able to relock from ANY version out there currently.
We don't know what's up with NPH25.200-23 for sure though... recently Moto has been doing "different" versions for Verizon users that don't seem to get to anyone else, we also see it in the Moto G5+, and we don't know the differences either. Most likely it's just a minor VZW specific change and can be ignored. If the update does get pushed later, you should have no issues taking the OTA update when on this firmware, it is the official factory image.

@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk

ghitus said:
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
As I stated in the first post... no, I have idea or information about any other images for other variants and I suggest following MotoFirmware123 on Twitter as that is the best place to find leaked firmware. Motonovo has gotten very tight on letting firmware get out, but if it becomes available this is likely where it will come from, IF it ever gets leaked.

Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks

Oaklands said:
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Click to expand...
Click to collapse
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.

acejavelin said:
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
Click to expand...
Click to collapse
Thank you. His phone is now ready.

Finally !Thanks, man!
Now I just flash via fastboot and avoid all the OTA updates process.
you are the man!