Database Info

[Help] XT925 failed to flash partition

Hi!
I have some problem for reflash my XT925.
He's unlocked on the bootloader and was rooted. I installed the last official KK ROM (from xda thread about update on KK). But my clock was stuck on the 1st January of 1970 and no way to modify that.
So I wiped the phone with TWRP and after I try to reflash my moto.
And it doesn't work! If i use the file for updating from 4.1.2 to KK, I have ann error with :
Code:
tz file size
And if I use the Retail FR 4.1.2 9.8.2Q-8-XT925_VQU-22
Code:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
If I delete these two files the flash works but the phone doesn't boot :'(
So I think my partition was corrupted and this is why I can't boot.
So how I can repair that. Some people tried to flash the GPT file from partition_signed file but I don't know where is mine ^^
Regards

No need to repartition system.
Flash the Retail FR 4.1.2 9.8.2Q-8-XT925_VQU-22 with RSDlite, then look for the OTA update.
If OTA update not available for your ROM, download the Edit.Blur_Version.98.21.22003.XT925.CEE-Retail.en.EU.zip which has the updater script included and flash it through your recovery.

Protman_40 said:
No need to repartition system.
Flash the Retail FR 4.1.2 9.8.2Q-8-XT925_VQU-22 with RSDlite, then look for the OTA update.
If OTA update not available for your ROM, download the Edit.Blur_Version.98.21.22003.XT925.CEE-Retail.en.EU.zip which has the updater script included and flash it through your recovery.
Click to expand...
Click to collapse
But it did'nt work when I try to reflash the partition (only the partition) it does'nt pass This is why I have this error
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
I need to reflash the partition but I was in KK. SO it doesn't want to flash a previous version I think. I need a KK official ROM to re-partition.

how did you install kk over what you had?

At first :
1/ Flash 4.1.2 Upgradable from here http://forum.xda-developers.com/dro...tutorial-make-motorola-razr-hd-xt925-t2916465
2/Upgrade via OTA to KK
3/Bug appeared with the clock and the date (unable to change the date or the clock (i'm not alone https://forums.motorola.com/posts/2b9452ac6b?page=1) )
4/Decided to wipe all for a clean flash
5/Trying to flash with the Retail FR 4.1.2 9.8.2Q-8-XT925_VQU-22
5/Flash Failed if I keep partition_signed (security downgrade)or tz file(wrong file size)
6/Flash Pass if I delete this lines in the xml but the phone won't start (bootloop)
Is it clear ?

much better Btrax, i can see clearly now
i just had that clock isht stuck in 1970 yesterday man, i did troubleshoot it for an hour or so, but I couldn't get it to adjust itself. In addition, i was doing more stuff even opening the xt 925 physically .
So after all the things i tried, i disconnected the battery to make sure i dont short circuit anything, then tightened up cables .
Rebooted the thing, and it fired right up.
I don't know how comfortable you are with getting into the xt 925, however with guidance, you don't even need to disconnect the screen cables or nothing.
You have two screws in the bottom, then you can just pry it open , and sideloading some plastic tool to disconnect battery and back.
I wish i had a softer solution but , it is what it is man. I ll be glad to help if you go that route.
ps. put link to this post in the link you shared

Since you are in France, there is a new recent OTA KK official update : 180.46.117.XT925.CEE-Retail.en.EU.
If I were you I would go back to Step 1 and 2 and then try to grab this new update.
Seems like it corrects Free Carrier EAP SIM and other Google security issues. Hope it will correct your problem too?

Protman_40 said:
Since you are in France, there is a new recent OTA KK official update : 180.46.117.XT925.CEE-Retail.en.EU.
If I were you I would go back to Step 1 and 2 and then try to grab this new update.
Seems like it corrects Free Carrier EAP SIM and other Google security issues. Hope it will correct your problem too?
Click to expand...
Click to collapse
In this update there is just je gpt file and no Tz file. so I need both I think because I flashe the GPT.bin file and after flash the Retail France ROM, but it didn't Work :/
So where i can find the tz file and gpt from canada?
My bootloader is unlocked so i can flash any official ROM

XT 1643 Downgrade Nougat To Marshmallow (100% Future OTA not Brick Your Device)

First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.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 userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem

prakash27091987 said:
First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.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 userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem
Click to expand...
Click to collapse
Downgrading only boot and system caused messed up fingerprint. Used all commands except bootloader provided in other thread for downgrade and now everything's good.

I see that the bootloader is not being downgraded. Doesn't that mean OTAs might still brick your device?

Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk

this is not working means fingerprint problem comes

Silesh.Nair said:
Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
So are you saying that the bootloader was updated and if we do the OTA we might brick our phone?

I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
The point about bricks is regarding downgrade. In previous phones, downgrading from L to K, but keeping the L bootloader and then getting official L OTA would brick phone. Motorola has never supported downgrade on any phone. So if you downgrade, and later take OTA you could brick. Especially if running M with N bootloader.
The whole title of this thread is wrong - no way can anyone 100% guarantee no future brick.

Silesh.Nair said:
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Taking OTA to official N from soak test N is not an issue, the issue arises when someone took the N soak test, downgrade to M, OTA to official N.
tl;dr if i'm not wrong:
M -> Official N = No brick
M -> Soak test N -> Official N = No brick
Soak test N -> Downgrade to M -> OTA to official N = Brick

When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
You can say what you want but go read the G And X2 communities. EVERY user that updated to M then rolled back to L and later took an OTA back to M bricked. The OTA doesn't take into a count that the bootloader was a newer version - I don't remember the mechanics, but the OTA expected a different version of the bootloader.
Search XDA or the Internet for "Blank flash files" . The problem is downgrade related. If you take any upgrade, be prepared to stay on it. Do NOT downgrade.

Well, it may be true. I don't just blindly flash files on my device. I go thru the zip file to see what files are patched to make sure that I don't get into trouble. That need not be the case with all users.
Let's wait for the official OTA to be released and then we'll see how it goes.
Sent from my Moto G4 Plus using Tapatalk

ok guys ive just done some testing and ive found that whilst on official android 6.0 my bootloader version was (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13
then after upgrading to 7.0 soak test the bootloader version changed to (moto-msm8952-b1.00) with the date 2016-06-24
so after i then did the downgrade back to 6.0 marshamallow and the bootloader version downgraded back to its original (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13 so moral of the story is the bootloader does infact downgrade too and doesnt stay with the new android 7.0 bootloader like many seem to claim on this thread if u guys want to try this for yourself run this command to get your bootloader versions before update and after u updateto 7.0 & then 1 last time when u downgrade to 6.0 u will need to run the below command via adb fastboot
fastboot getvar version-bootloader

The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147

chromedome00 said:
The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
soo we cant take ota but we can install it manually that doesnt effect i think

does downgrading work if my device is brick??
does downgrading work if my device is brick??

sucssecfully downgraded from marshmallow after brick in nougat .........tons of thank
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....

drdhaval1987 said:
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....
Click to expand...
Click to collapse
dOWNGRADE process please

kemesh said:
dOWNGRADE process please
Click to expand...
Click to collapse
its already mentioned in this thread....simply follow the steps........

When I am trying to install the Nougat OTA zip file from within the stock recovery, it is giving me the following errors:
Code:
Verifying current system. . .
Mount count = 9
Last mount path = /system
Last mount time = 1479061757 -> Sun Nov 13 18:29:17 2016
Device was remounted R/W 9 times
Last remount happened on Sun Nov 13 18:29:17 2016
E1004: system partition fails to recover
E: unknown command [log]
E: unknown command [log]
E: Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I go about fixing this? I have followed your guide on how to downgrade and downgraded my XT1643 to -63 baseband.
Help please!

[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

[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!

How to unbrick you hard bricked moto g4 plus (with February+ update) x1643

*Temporary solution can unbrick your moto g4 plus*
This is temporary solution Mixing new gpt and bootloader for unbricking xt1463
You will need dummy bootloader to installed on your device before proceeding !
No need to download full rom if you just want to unlock your bootloader you can us this method
https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view
Above link is for gpt and bootloader of 2018 April
How can you unbrick your hard bricked g4 plus
Tested on 16gb variance x1643
Requirements :-
ADB FASTBOOT
Download that gpt and bootloader
Procedure:-
Extract adb and gpt and bootloader in same folder then hold shift and right click anywhere to open command prompt in that directory
enter following commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Then flash your rom any version i used
ATHENE_NPJS25.93-14-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
this version with
NPJS25_93_14_18_April2018_GPT_bootloader
this gpt and bootloader and my device booted am gonna download
NPJS25_93_14_18
Rom later tomorrow
Link where i got gpt and bootloader !
https://forum.xda-developers.com/moto-g4-plus/help/bootloader-yellow-alert-t3823085/page2
Need help ?
More info ?
Comment Below !

You might like to directly flash the NPJS25.93-14-18 April 2018 stock firmware after flashing the April 2018 GPT and bootloader, and not advise to flash older firmware. The reason is the April 2018 GPT/bootloader is from the NPJS25.93-14-18 firmware, so you're not mixing and matching GPT, bootloaders and firmware - if you are mix and matching firmware, that may lead to more bricking if you're not careful. Link to the NPJS25.93-14-18 firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Of course, if you flashed the Oreo soak test at any point using the OTA updates, this procedure may not work. If you used the TWRP flashable, you may be okay if you did not use the Oreo OTA update - TWRP flashables don't update the bootloader. The Oreo OTA would update your bootloader to Oreo, which we don't have the GPT/bootloader files for yet.

echo92 said:
You might like to directly flash the NPJS25.93-14-18 April 2018 stock firmware after flashing the April 2018 GPT and bootloader, and not advise to flash older firmware. The reason is the April 2018 GPT/bootloader is from the NPJS25.93-14-18 firmware, so you're not mixing and matching GPT, bootloaders and firmware - if you are mix and matching firmware, that may lead to more bricking if you're not careful. Link to the NPJS25.93-14-18 firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Of course, if you flashed the Oreo soak test at any point using the OTA updates, this procedure may not work. If you used the TWRP flashable, you may be okay if you did not use the Oreo OTA update - TWRP flashables don't update the bootloader. The Oreo OTA would update your bootloader to Oreo, which we don't have the GPT/bootloader files for yet.
Click to expand...
Click to collapse
Actually i didn't had link for new fireware i searched on firmware.centre i didn't got any latest version so i tried this mixing gpt and old firmwares and it worked for me
that's why i typed there temporary solution
Thanks for reply though ! <3