yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] ResistanceIsFutile:
Really... How can you ask this !

I'll play your game - Install what exactly ???

Please read all things my fellow XT1572 Moto X user and understand it.

Seriously,

NO -- to an (XT1575) Factory IMAGE going to/in/on a XT1572 Indian device.

The Guide acejavelin offers gives you links to various variants of an official factory firmware, like for the XT1572.

If the link (courtesy of Prazaar) gets a "404" - try the link for "Alternate firmware source for Pure and Style" in same paragraph as the other links...

Or search through X Style (Pure) General for what factory image build you need.

I have no ideal what build version number your at now but, you need a factory firmware image that is the same version number or a newer version than what you have installed and it being specific to your Moto X device model's variant.

Along with acejavelin's guide advise-,

"The procedure for other XT157x device like the Style would be identical, except substitute your appropriate factory image.

Note that different firmware's versions may contain a different number of system.img_sparsechunk.X files, you must flash the correct number you have in your firmware image already installed, and in their proper order to the device again in going back to a stock environment.

But always verify with the XML flash file contained within the firmware archive to know and if you are in question as to the number of system.img_sparsechunk.X files."

If your confortable with a guide made for the XT1572 device see this one .

Compare both guides and the given advise and to understanding it all before going any further in the flashing process.

We don't read minds here - so if you want to know anything more, please be as specific about all parts in what your questions deal with or their subjects for the best help.

Hope all of this was crystal clear :cool:

**************************************************************************************************

------------------------------------------------------------------------------------------------------------------

**************************************************************************************************

I believe I'd run down an understanding first of the cause or source to it happening - otherwise it may go with you to the Nougat.

something like-

devices age

accidental drops landing on the screen

screen failure

security on the device or it's files/partition getting corrupt

possibly an added app

Seems like I've read this before happening to this device, though, my recall isn't clear where or on a stock OS or in a custom ROM.

What have you got to loose in a factory reset - if your thinking of flashing the Nougat OS now?

I'd even try a stock MM flash and see if it's still happening to the device.

Your device and call.
[X Style (Pure) General] aybarrap1:
I think I didn't clarify myself well. When the lockscreen acts up I turn off the device and back on. Sometimes just a couple of times does the trick... Sometimes 5 or so. The lockscreen issue only occurs after booting up and after x number of turning off then on, it starts working perfectly fine until the next time I restart the device. This is not occuring at random times during daily use and the screen functions normally. One symptom that always occurs as well is that my wallpaper changes to the default factory one after a some restarts and that is when I usually get the lockscreen working again

The only thing that roughly correlates time wise is an update to Magisk. I noted a couple of people said they had some issues with v17.

While I could just factory reset, I've been intending to switch to stock nougat for some time. However, I was comfortable with my setup and just didn't care to go through and put the time in. Between work and family, other things took priority.

Worse case scenario that you pointed out is that the hardware is failing and flashing nougat will not help. If that is the case, I'll move on to another device much sooner.

Thank you for your input.
[X Style (Pure) General] rajibie:
Actually I'm on stock NOUGAT version with October 2017 patch. Just want to convert my xt1572 to xt1575 variant. I read that on stock NOUGAT of xt1575 volte works but on xt1572 it doesn't work. So just wants to check if volte works by converting to xt1575
[X Style (Pure) General] ResistanceIsFutile:
[MENTION=2444885]aybarrap1[/MENTION]

Your welcome :)

I got that it's not occurring at random times during your daily use but, mostly when restarting or booting up.

I totally understand it's a pain to deal with, and I offered you what I'd do to understand it or troubleshoot it.

Though, with your new mention of the wallpaper changes to the default factory one - have you changed it with the factory options or in using an installed app (themer app of sorts ?).

If so, just try uninstalling - disabling it (themer app).

Next, if phone is in your control/possession most always try disabling the lockscreen function you've set and run without it.

These along with the other things I've already mentioned could led to more time using the device without as much hassle, and avoid the replacement costs sooner.

It doesn't take all that long to ADB/Fastboot a stock image - just making the time to do it.

Already got your ADB/Fastboot platform-tools directory folder on the PC and the stock firmware image downloaded, 10-15 minutes tops if it goes smooth the first time.

If by chance you do have some partition corruptions - flashing a stock firmware will re-write them all.

More so than a TWRP restore does, as TWRP doesn't backup all the devices partitions anyways...

Hope this has made sense to you. I do try to help when I can and thank you for thinking so.

PS: I believe where I'd seen the XT1575 mentioned with lockscreen troubles, was a custom ROM that the wakeblock app needed to be disabled or deleted from the root of the ROM.

Specifically the NucleaROM - as one of the items the wakeblock app made misbehave. Otherwise a good stable ROM for Nougat modems.
[X Style (Pure) General] ResistanceIsFutile:
[MENTION=4213978]rajibie[/MENTION]

I believe any answers correct or not - are not going to come in a thread for the Moto X Pure XT1575 Factory Firmware Nougat NPH25.200-22, since your interested in XT1572 experimenters (trail-blazers) trial and error words...

Doing other than the normal stock firmware flashing on the XT1572 device, as you don't want to listen to trusted advice that acejavelin offers people and would know.

[[The procedure for other XT157x device like the Style would be identical, except substitute your appropriate factory image.]]

You want Trail-Blazers and/or Experimenters words then good luck to you as you'll need it.

Probably be lucker posting a question in the X Style (Pure) Q&A, Help & Troubleshooting and get some answers.

Something like a question of-

Has any XT1572 user tried to flash a stock XT1575 firmware image to the XT1572 Indian device ? With success ?

Telling your position further of why...

I'm on a stock NOUGAT firmware version with an October 2017 patch for the xt1572 and want to get my volte working.

I've read that on the stock NOUGAT for the xt1575 device the volte works but, on my xt1572 it doesn't work.

So I just want to check if I can get volte working by converting my xt1572 (Style) variant to an Stock Nougat xt1575 (PURE) firmware image and it's possible.

--------------------

Additional info to you only...

Notes - we don't even have an Official stock firmware build that has the Oct. 2017 security OTA in it for our XT1575 device to flash it - least nothing OFFICIAL leaked.

We have to flash the CLARK_RETUS_7.0_NPH25.200-22_cid9_subsidy-DEFAULT_CFC.xml.zip and stay totally stock till the security update (Oct 2017) patch comes from the servers.

Taking us XT1575 users from a build number NPH25.200-22 and security patch level Sept. 1, 2017.

To the build number NPHS25.200-22-1 and the security patch level Oct. 1, 2017.

Off beat chance and a totally different device-

Quiz this thread

If you could dissect the two firmwares of xt1572 and xt1575 for Motorola and understand what differences there are to make a mod to yours.

What part(s) to look at, etc...

Off beat chance and gamble like I said - anything (this or what you want to try) would be a risk to an inoperable device as I see it.
[X Style (Pure) General] aybarrap1:
Thanks for the update.

I haven't tried disabling lockscreen because of Google pay. I could live without it but honestly, I think I have just been waiting for a good excuse to flash nougat.

As far as the time involved, that is more related to setting everything back to the way I like it with the bulk of the time really just waiting on things to download. It is not a huge deal really.

If for some reason it is a failing device, I will move on. I have the means to replace it today with devices that strike my interest but if it is working well I just can't justify moving on quite yet.

UPDATE: After just over an hour, I am now on Stock Nougat rooted with Magisk and TWRP installed. The actual method to go to stock Nougat in this thread actually only took about 10 to 15 minutes while the rest of the time was doing backups, downloads, and setting up TWRP (and backing up stock ROM w/ recovery) and Magisk. The rest is just letting my apps finish downloading and restoring certain backups. All the little things I will take care of over the next few days as I need apps.

Thus far no lockscreen issues and I have rebooted several times now.

BTW: the instructions on the OP was perfect. As I went through each line I made sure it went through okay. Only one failed so I flashed again immediately and it succeeded so I moved right along. The first boot took longer than the actual flashing portion.
[X Style (Pure) General] aybarrap1:
I am liking the update well enough but definitely don't feel as if I missed too much while putting it off. Split screen is not really a thing for me but the notifications I like a little better. I had a location setting problem where it would disable after restarting the phone but I finally found the setting that was causing it.
[X Style (Pure) General] kerdiaz:
Hello, i'm having problems again with this rom. i'm putting the commands in the order and checking if said OKAY.

Here's my log

https://pastebin.com/EZmDpPrS
[X Style (Pure) General] stevejohnson42:
Believe issue is here :

=====================================

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:modem: not found

target reported max download size of 536870912 bytes

sending 'modem' (41725 KB)...

OKAY [ 1.107s]

writing 'modem'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 1.138s

===========================

when you do the flash and get a fail - just retry the command again - you do not have to start over

For me - this is the place that is most common to get a fail

Hope that helps
[X Style (Pure) General] kerdiaz:
Thanks, i reflash the command again and my phone install the ota. Thanks.
[X Style (Pure) General] aybarrap1:
[MENTION=5781153]ResistanceIsFutile[/MENTION]: Thanks for the rundown. I had read about most of these. I already use system UI tuner and it has received some improvements over MM which I can appreciate. The last app access by double taping the square is also convenient.

Data saver and split screen are cool features but I just don't use them.

I'm sure the enhanced doze mode helps as I'm sure other features do their part as well.
[X Style (Pure) General] ToTheRoot...:
I don't understand
[X Style (Pure) General] kcv_earner:
Saved my bacon? actually clark.

Thanks for posting this info. This saved me a couple of times last week when attempting to get LOS flashed. :)
[X Style (Pure) General] Jman47:
This 200-23 file fixed it

THIS SAVED ME.

Locked Bootloader (had 'Allow OEM Unlock' in Developer Options. error)

firmware on 200-23. was bootlooping without an OS.

was able to fastboot and ADB soI tried everything on the forums but everyone only had 200-22 available.

i downloaded this file and everything flashed perfectly. was able to boot and "allow oem unlocking " used my code and unlocked the bootloader

mirror for download :https://drive.google.com/open?id=16LD16SS9hNqIAD6DHTgi8PVsghe-s_bd
[X Style (Pure) General] jrredho:
Now it's time for me to thank you! The original mega.nz download link didn't work for me today, but your quoted link worked just fine. (Btw, I did double check the sha1 hash as well.)

I haven't looked at messing with my phone in quite a while; for the most part, I've forgotten how. But I'm thinking of re-rooting to update Ad Aware and to once again be able to use OS Monitor, and hadn't saved this latest firmware file anywhere in case I run in to problems. Now I have. :)

cheers,

john
[X Style (Pure) General] R77:
So the Google drive zip link is a new version of the nougat firmware?
[X Style (Pure) General] kngharv:
Dear all:

I want to share my experience.

In short, I deeply regret of flashing to the new 7.0 ROM. The number one reason why I deeply regret it is because the vast majority of 3rd party ROM, including the official LineageOS/14 ROM are incompatible with the new 7.0 firmware boot image (and partition?).

I can not get Magisk to work on this 7.x firmware neither. Everytime I tried to root my phone using Magisk, the phone end up in boot loops.

The worse part is that I can't simply go back to the older version of the firmware.

Secondly, I encounter a very strange problem using this particular ROM (7.0_NPH25.200-22): The ROM itself from the first glance seems to be fine. I went through the set-up, and do an immediate update on all built-in apps.

The issue is that these updates are not persistent! Every time I reboot the phone, I lose *ALL* my update and I would need to update the built-in app all over again!

Further, the 3rd party apps also not persistent. i.e. SOME apps simply disappear after I reboot the phone, as if I have never installed it. Other apps will constantly give me error because it relies on updated library such as Google Play Services, but the rebooted phone no longer have the newly updated Google Play Services installed.

I couldn't get around with this issue using this ROM.

Luckily, I found a copy 7.0_NPH25.200-23. Once I flashed the 7.0_NPH25.200-23, I no longer have that issue (I avoided the radio/modem part of 7.0_NPH25.200-23 when I flash the ROM)

I still couldn't get Magisk to work. But given that no other 3rd party ROM (aside from the unofficial Pixel Experience/11) can even boot into the system, I am just glad at least the stock ROM works.

I never test the radio part of the phone. My phone is a Chinese variant dual SIM. I never expect the SIM part of phone to work at first place. For my own repurpose goal, all I needed is wifi, and the 7.0_NPH25.200-23 ROM served my purpose (while the Pixel Experience does not. Many apps simply crash out and the phone is too slow to run).

If any of you have similar experiences, and/or better, figure out how to get Magisk to work and knows which 3rd party ROM can be flashed on this 7.0 firmware, please let me know here.

ps. If you guys can't find 7.0_NPH25.200-23 ROM image on the internet, I'll see if I can put it somewhere.
[X Style (Pure) General] Bill720:
If you can find that image, let me know. I'd be quite interested in receiving it.
[X Style (Pure) General] kngharv:
CLARK_RETUS_7.0_NPHS25.200-23-1_cid9_subsidy-DEFAULT_CFC.xml.zip

drive.google.com
[X Style (Pure) General] Wheels564:
The official Lineage 14.1 will not work with the Nougat bootloader since it is based on the MM bootloader. If you want to try Lineage you will need to download TWRP 3.3.1-0 and flash the latest Lineage 14.1 based on Nougat bootloader. https://xdaforums.com/t/rom-officia...-moto-x-pure-2015-clark.3513299/post-85720255

These were the last roms to work with the dual sim and VoLTE. I'm not sure how it will work with the Chinese variant so make sure you do a backup once you install TWRP including the EFS partition.
[X Style (Pure) General] Bill720:
Terrific! Thanks. I was getting errors trying to install the -22, so I might have better luck with the 23.

UPDATE: It worked!
[X Style (Pure) General] cmulk:
removed
[X Style (Pure) General] acejavelin:
A link to full flashing instructions is included in the OP... The reason you had to do this is you didn't do the COMPLETE flash, you didn't do any of the wipes.

The PROPER way to flash is:

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

And you won't have any issues like you noted. The details are clearly laid out in the "flashfile.xml" that is included in the firmware image zip file.
[X Style (Pure) General] CLETjB:
I'm having Data connectivity issues with this build, if I put my SIM in and another MXPE it with a OTA push it works fine.

The only difference I can see is that the Baseband version is different, on the good phone it's M8992_1255331.29.01.88.09R SUPER_NA, and on the Bad phone I have M8992_1255331.29.01.88.02R SUPER_NA

I was on IM Chatting with PP Tech Support trying to get it working, but it's On/Off Up and Down from 1x to LTE to OFF anf keeps cycling..

The phone was somewhat working with the OTA, but then I flashed it to get a Clean install so I can setup Magisk with it.
[X Style (Pure) General] ptn107:
M8992_1255331.29.01.88.02R is the marshmallow (6.0) modem.
[X Style (Pure) General] CLETjB:
Ok, I flashed the M8992_1255331.29.01.88.02R that came with this attached Factory Image, and I still can connect, now my WiFi will not shut off. The phone was working fine with the MM and the OTA
[X Style (Pure) General] acejavelin:
This build includes M8992_1255331.29.01.88.09R SUPER_NA modem firmware... If you have something else, you did not flash it correctly or the firmware didn't get written properly, or possibly when you extracted the files you did not over-write them properly.

When you flash the "modem" you need to flash the entire modem firmware stack... NON-HLOS.bin and fsg.mbn *MUST* be flashed together as a pair.

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin

And verify an OKAY response after each step.
[X Style (Pure) General] CLETjB:
OK, I'l Re-Flash it, without the Lock commands and see what happens

---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------

What does the:

fastboot erase customize

fastboot erase clogo

Do?

---------- Post added at 01:28 PM ---------- Previous post was at 12:51 PM ----------

Ok, I flashed it again with the script in this thread, and during the initial Google 2-Step Verification I don't get the code, I have to insert my Sim in another phone to get the code..
[X Style (Pure) General] acejavelin:
I don't know what those two commands do exactly, except erase those 2 partitions... they are in the `flashfile.xml` that is contained in the archive so they are part of the process.

What script? This isn't a script, each step needs to be done manually and you need to verify an OKAY after each step... If you are copy and pasting the whole thing it will fail.

If I were you, I would re-download the ZIP, extract it to a new folder (say C:\nougatfw\ assuming you are using Windows) and reflash the device one step at a time:

fastboot oem lock begin (if wanting to re-lock bootloader, othewise use `fastboot oem fb_mode_set`)
fastboot flash partition C:\nougatfw\gpt.bin
fastboot flash bootloader C:\nougatfw\bootloader.img
fastboot flash logo C:\nougatfw\logo.bin
fastboot flash boot C:\nougatfw\boot.img
fastboot flash recovery C:\nougatfw\recovery.img
fastboot flash system C:\nougatfw\system.img_sparsechunk.0
fastboot flash system C:\nougatfw\system.img_sparsechunk.1
fastboot flash system C:\nougatfw\system.img_sparsechunk.2
fastboot flash system C:\nougatfw\system.img_sparsechunk.3
fastboot flash system C:\nougatfw\system.img_sparsechunk.4
fastboot flash system C:\nougatfw\system.img_sparsechunk.5
fastboot flash system C:\nougatfw\system.img_sparsechunk.6
fastboot flash system C:\nougatfw\system.img_sparsechunk.7
fastboot flash system C:\nougatfw\system.img_sparsechunk.8
fastboot flash system C:\nougatfw\system.img_sparsechunk.9
fastboot flash modem C:\nougatfw\NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg C:\nougatfw\fsg.mbn
fastboot flash bluetooth C:\nougatfw\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

And verify an OKAY after each step... if you are still having problems we will need a copy of your attempted flash from the terminal (the whole log) and a copy of the output from `fastboot getvar all` with the IMEI masked out.

We know the file is good, several people have used it successfully now.

If the issue is just with Google's 2-step authentication, try disabling it temporarily...
[X Style (Pure) General] CLETjB:
Each command separately, din't fix the problem, is there a way for me to re-install the Last MM 6.0 build and take the OTA, that worked, before.
[X Style (Pure) General] acejavelin:
Honestly, I don't know... My understanding is that downgrading to 18-8, then applying the 18-16 OTA zip is possible, but if you take the OTA to Nougat again it will brick, or something like that. This file is literally what people were waiting for to fix that issue. Although I could be wrong, maybe someone else can clarify.

I am still unsure why this failing, and without your terminal log and output of getvar all I can't tell you. This really sounds like a classic case of mismatched boot.img and the radio firmware though. What radio firmware does getvar or the Phone Info screen show you have, and what kernel?
[X Style (Pure) General] annoyingduck:
[MENTION=2001582]acejavelin[/MENTION] big thanks for tracking this down. This is like the holy grail for our aging device!! I got to tell ya, I'm so confused as to why there is another build that Verizon folks have supposedly been getting ( NPH25.200-23 vs NPH25.200-22). I'm on Verizon but I've been running NPH25.200-22 since it dropped and have not gotten any type of OTA for this mysterious -23 build. How on earth does a universal unlocked device get a carrier specific build? Moto doesn't know what carrier we're on at time of purchase. It just doesn't make any sense to me. The only thing that makes sense to me is that all devices will get the NPH25.200-23 build. Otherwise, how does a Verizon user transfer to another carrier? SO Strange!! Anyways, when I have some downtime I'll do a clean fastboot flash of the full factory image and see if I get an OTA to the -23 build (I'm on Verizon). If I do, I'll capture the OTA from -22 to -23 and post it here. I'm not so sure though that the -23 OTA will even come if your running -22...It may require being on the 8-16 Dec. build. Again, the whole thing is just weird. What are your thoughts?