yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] acejavelin:
I don't know... it's odd, but we see the same thing in the G5+. There is a Verizon build, and a build for everyone else. Right now a lot of VZW users are stuck on an older build and awaiting an update, it's almost like there are two unique software streams but you can still take the phones back and forth between carriers. It's rather confusing.
[X Style (Pure) General] acejavelin:
You didn't get OKAY after NON-HLOS.bin, you need to repeat it, up to 3 times until you get an OKAY... It's not unusual to fail the first time or two.
[X Style (Pure) General] CLETjB:
Just that file or the whole Room?
[X Style (Pure) General] acejavelin:
Try just the file, you might have to erase the modem state files first... I remember other people having issues with this on some stock ROMs in the past. Try to flash just the modem file up to 3 times, if it still fails, clear modemst1 and modemst2 and try to flash it again a couple times.

If all that fails, do the whole thing, and try flashing that one piece until it gives an OKAY, it can take 2-4 times for that file.
[X Style (Pure) General] chrisn812:
I know its probably been asked in other threads but how does this perform over LOS 14.1? Battery and responsiveness? Thanks! I'm planning on flashing this tomorrow.
[X Style (Pure) General] acejavelin:
It's stock... Well optimized, rock stable, typical Moto ROM. Most people think it's better than Marshmallow. It's not a custom ROM so customization options are limited.
[X Style (Pure) General] chrisn812:
Thanks. I don't customize to much. Rather have something stable that I can get another 6-9 months from my Pure. Tired of some of the glitches with LOS. Bluetooth and camera being the main issues.
[X Style (Pure) General] autosurgeon:
Yeah it's Rock solid for me. With Facebook lite or even better no facebook it's even pretty battery friendly.
[X Style (Pure) General] cmulk:
Good point, I removed my original post to avoid confusion. The flashfile.xml is also the order I followed to do the flash. The main reason I avoided erasing userdata is that I didn't want to delete my Internal Storage. Is that right that erasing userdata formats Internal Storage as well?
[X Style (Pure) General] acejavelin:
Yes, that's correct.
[X Style (Pure) General] Un4k3v1n:
Worked perfect on XT1575

Worked like a charm. Thank you very much, sir.
[X Style (Pure) General] CLETjB:
Tried doing what you suggested, and the SIM (Cellular) is still On/Off, nothing stable.
[X Style (Pure) General] StankFiss:
Been running this for couple days. Runs smoothing than what was said on the Lenovo site. Noticed some odd though. Ive never got Verizon quick numbers on my phone dialer before. Numbers like tech support blah blah blah. This is the first time for any non Verizon firmware to do this. O well, running good.
[X Style (Pure) General] acejavelin:
Really? Usually they are SIM contacts, look where they stored.
[X Style (Pure) General] acejavelin:
Don't know what to say... Others have no issues.
[X Style (Pure) General] autosurgeon:
If you are having stability issues factory reset is a must.
[X Style (Pure) General] StankFiss:
Yeah search google contacts and was nothing. Struck me odd that it showed up. Easy fix was to deleted. I flashed twice cause I muffed the first trying to get root. Both times it showed up in contacts.
[X Style (Pure) General] mddunner:
Apologies if this is off topic, but I've been trying to determine if stock 7.0 is similar to 6.0 with notifications / ambient display. Is the notification LED used in 7.0 or is it still ambient display only?
[X Style (Pure) General] autosurgeon:
Ambient display only.
[X Style (Pure) General] chrisn812:
Very pleased with it now 24+ hours in. Running solid, not a single glitch when paired up to the half dozen bluetooth devices I use throughout the day. Ambient display is a bit annoying. Rooted with MagiSK 14.3, patched tethering. All good with the X now. Just wish it had newer security updates but I can live with this until I decide on a replacement.

Does LOS support the new 7.0 baseband/modem code? I first tried just flashing those on my existing LOS 14.1 install and got no where. Then flashed the whole NPH25.200 package for a clean install. May try experimenting with that when my work on-call rotation ends next Monday.

Thanks everyone for the code! Happy to have it.
[X Style (Pure) General] acejavelin:
There is no notification LED on this device... The LED is hardwired to the charging circuitry, it is not possible to use it as a "nomal" notification LED.
[X Style (Pure) General] acejavelin:
Moto Display can be disabled in the Moto app.
[X Style (Pure) General] Andvark:
Actually the LED can be used for notifications. Some custom ROMs support it; I have been using it myself for a long time.
[X Style (Pure) General] acejavelin:
I didn't say it couldn't be used... I said it's not a Notification LED. It can be used while connected to external power (charging) as a notification LED. Personally, that's not of much interest to most people.
[X Style (Pure) General] Andvark:
My mistake; when you said that it is "not possible" to be used as a normal notification LED, I took your meaning to be that the LED couldn't be used for notifications. The phone does not need to be connected to external power for the LED to be used for notifications (missed calls, texts, etc.), btw.
[X Style (Pure) General] StankFiss:
Charge , sd card that's it for notification. Now there are third party apps out there to make the flash notify you for calls, text and voice mail. Btw nice hi-jack of thread. Back to topic.
[X Style (Pure) General] Andvark:
I didn't mean to offend you; the only reason I said anything at all was because you, the OP, initially made the comment, and I wanted to set the record straight. Otherwise I would have considered it hijacking the thread and kept my mouth shut. So let's just leave it at that I respectfully disagree with your statement and move on.

EDIT: Sorry, just noticed that you aren't the OP. Anyway, what I said still stands.
[X Style (Pure) General] aBowlaPuddin:
im sorry if this has been asked already, i did look. but, can i downgrade to marshmallow or flash a custom rom over this update?

thanks!!
[X Style (Pure) General] acejavelin:
It's not recommended... You can downgrade skipping bootloader.img and gpt.bin but if you take an OTA it's hard bricked. As far as custom ROMs go, same rules apply and only a couple have support for Nougat radio stack so you would have to downgrade just the radio stack portion.
[X Style (Pure) General] aBowlaPuddin:
thanks, im trying to figure out some thing. I recently upgraded to a new device and when i went to sell this one. I had just clean flashed to TruPureXMM 2.9 but it wouldnt let me download anything from the play store. Unfortunately, i only found that out after i let someone else log there google account in to check it out before buying. I figured i would just update and get it back to stock so i shouldnt have that issue again. But i didnt know about "Factory Reset Protection" until trying to set it up after the new update. Now i cant get past the set up to even check out that everything works.
[X Style (Pure) General] acejavelin:
Yeah, this won't help then... FRP can't be bypassed on any MXPE after February 2016 update. You need to contact that person and get them to clear it out for you by logging into the device, add their Google account in, then remove the Google account before factory reset.
[X Style (Pure) General] umlguy:
I still do not have the it's 7.0. this phone no longer has a working sim, it was on at&t though. Does it have to have a working sim to download the update?
[X Style (Pure) General] StankFiss:
This is not a OTA download. Does not matter what carrier or if you have a sim in or not. This is a fastboot flash firmware. This is done through your bootloader. If you use this it will delete everything on your phone and will start from a fresh Nougat image. This link is to a side load or stock recovery OTA update and you will be able to keep everything on the phone. https://xdaforums.com/moto-x-style/general/guide-xt1575-update-to-nph25-200-22-t3680477 Either one you do not need a sim. Give thanks to [MENTION=2001582]acejavelin[/MENTION] and [MENTION=4795150]annoyingduck[/MENTION] for finding these files.
[X Style (Pure) General] Jujuette:
Moto x pure finally updated to 7.0

It's Nov 20, 2017, and my Moto X Pure Edition is just being updated to Android 7.0 at 530p! Android 8 was released months ago and no doubt android 9 will be out soon!! I guess the old adage of 'better late than never'.....can be applied to my very late update!
[X Style (Pure) General] psychoboy:
In case this helps anyone... I am a T-Mobile user and have been waiting forever. I was probably seconds away from taking the plunge and loading this when the OTA notification popped up on my phone a few hours ago. I tried to download it by using logcat, but failed as I could not find the right link until after my phone had gotten it, and as soon as it got it the link would not work. However, I did notice that the version that I got is newer, 25.11.23.en.US. The version name that I was able to grab out of the logcat file was, "Blur_Version.25.11.23.clark_retus.retus.en.US", or I also saw "NPH25.200-23".

To early to comment on performance, but I have always had a problem with available memory and it seems to have fixed that. Maybe by deleting some older update files that were left behind? I barely had enough space to do the upgrade, it needed 960MB. I deleted all photos and an app to barely make that number. Then, after the update, I have 3GB available. Cheers...
[X Style (Pure) General] el7145:
Updated over the weekend on a us factory unlocked moto xt1575 with a cricket sim, everything went smooth as silk, thanks for. The detailed instructions and file.

FYI, my moto had never been rooted nor had its bootloader unlocked
[X Style (Pure) General] Kpenguin.5284:
Does your method for rooting still work after the update?
[X Style (Pure) General] annoyingduck:
[MENTION=2001582]acejavelin[/MENTION] according to many G+ post's I'm seeing, it seems that T-mobile users are getting the -23 update version (and Verizon as stated before). If you happen to see the full firmware or the OTA zip for that update, please let us know. I'm hoping someone with root can grab that OTA file. I've tried clean flashing the -22 build (I'm on Verizon), but did not get an OTA notification for -23. I'm setup now, so I won't try it again until I have some more time, but I may have to go back to MM and OTA up in order to grab this -23 OTA zip.

Maybe someone with root can kindly extract the .23 OTA and upload it for us before they install it and save me 1/2 a day of triggering the OTA manually...
[X Style (Pure) General] acejavelin:
From what we have seen, .22 and .23 are almost identical, except for a change in the radios that no one has seen a difference in yet. No one with 22 has seen an upgrade to 23 either, so getting the OTA file isn't useful if you are already on 22. Remember OTA's are delta updates and can only be applied to specific versions of software, this one (NPH25.200-23) can only be applied to the 18-16 Marshmallow firmware.

We don't know if people with 22 will see an upgrade to 23, or if Moto will see them as functionally equivalent and not bother to upgrade (this has happened with other devices).

Honestly, don't expect this factory image to surface for several months and most likely not year this for sure, if it ever does show up, just like it took .22 forever to surface. Again, Moto is very tight about factory firmware images now, a "leak" is the only way they get out now. For the best info, follow Motorola-Firmware-Team's Twitter feed.
[X Style (Pure) General] annoyingduck:
So maybe what I can do (if I really want the -23 update) is to downgrade to MM -8 and OTA to -16, which should trigger the -23 OTA as I'm on Verizon. I'd like to just have the -23 OTA update zip. However, -22 is running just fine for me on Verizon and I like knowing that the full firmware is available for it.

On a side note, I was thinking of learning how to make a TWRP flashable zip that contains the MM-16 radio/bluetooth files only for people that have upgraded and want to easily downgrade the proper files in order to run custom roms. Which files exactly need to be added to the updater script? The modem NON-HLOS.bin would need to be flashed, the bluetooth BTFM.bin would need to be flashed, but what about the fsg.bin (I'm not sure what the even is)? Then the updater script would also need to include the erase modemst1 & erase modemst2 commands also somehow, and those commands would need to be executed after the modem flash. I'd also have to be sure that the META-INF folder is commanding the right partitions to be flashed, just using META-INF from say a custom rom would only have the right paths for /system and /boot. Any Moto users you'd recommend I chat with to be sure I'm writing the command script correctly?
[X Style (Pure) General] acejavelin:
If you downgrade to Marshmallow and take OTA to Nougat, it will hard brick.
[X Style (Pure) General] annoyingduck:
Oh, I did not know that. Downgrading is bricking phones, has this been confirmed or just a few cases of it? Surprising, as most motos can be downgraded.
[X Style (Pure) General] acejavelin:
Downgrading is fine... it's the taking of the Nougat OTA again that is doing it. Confirmed too many times...

What happens is you have to skip gpt.bin (partition table) and the bootloader and flash the rest of the ROM to downgrade, that works fine... but for some reason, whatever the Nougat OTA upgrade script does messes up the bootloader and it hard bricks. Only remedy at this time is a mainboard replacement.
[X Style (Pure) General] SoNic67:
Are the VoLTE and HD Voice working?

All the LTE bands, including 13? This last one can be checked with Cellmapper app (on Nougat it does not require root to show the actual LTE frequencies in use).
[X Style (Pure) General] acejavelin:
It has been tested many times in varying locations on Verizon with 22 software... VoLTE, HD Voice, and all compatible, supported bands in Verizon function normally. At this time we don't know why Verizon didn't approve 22 software and did approve 23, but it seems not really carrier specific because AT&T and T-Mobile did the same thing.
[X Style (Pure) General] emaxxim:
[MENTION=2001582]acejavelin[/MENTION] sorry to bother you but I'm searching the full stock nougat firmware for Moto X Style. How did you take this for Pure? Maybe I could replicate. Thanks.
[X Style (Pure) General] acejavelin:
I didn't do anything... It was leaked to the Moto Firmware Team, I have nothing to do with it. We have ZERO control over getting these ROMs at all, if we can get one leaked, great... If not, I'm sorry but we have no control over it.
[X Style (Pure) General] StankFiss:
So if we upgraded to .22 nougat we will not see the .23 update?
[X Style (Pure) General] autosurgeon:
No one knows the answer to that.
[X Style (Pure) General] SoNic67:
Who knows? It must be something obscure, that most people won't notice. Since I am on a Verizon MVNO, most of the features are not enabled anyway - like VoLTE, HD Voice, roaming on rural LTE...

Even if Verizon had recently some disagreements about that last one: https://www.rvmobileinternet.com/verizon-terminating-certain-rural-customers-for-excessive-usage/
[X Style (Pure) General] ech1253:
NPH25.200-23 & LineageOS 14.1 (Clark)

Despite having un-rooted and returned to XT1575 to MM stock, re-locked (and software shows "official"), as of today I was still not offered any OTA via Wifi (my Moto X hasn't been in use since May). So, to try to ensure I get the .23 release OTA I borrowed my son's T-Mo SIM and was immediately offered the OTA (25.200-23). I do not have root at this point so I can't seem to save the file to upload for others (if you know how, without root, please let me know).

Before I apply the OTA, I wanted to ask if anyone HAS taken the .23 OTA and then re-rooted and installed LineageOS 14.1 (Clark, obviously)? I rooted my SM-T800 (Tab S) with LOS a few months ago and like the regular builds that include the latest Android Security Patches, so I am hoping to address my long-standing concern over being seriously behind on security patches on the XT1575 since I bought it (isn't that one of the reasons we bought these?).

Just curious if anyone is running .23 with LOS 14.1 and what, if any issues, they are seeing? Did you DL LOS directly from https://download.lineageos.org/clark or are you using a variant (did I read that Hashbang is maintaining a separate build?)

Anyway, sorry for rambling a bit, just curious on feedback of the above? Thanks in advance!
[X Style (Pure) General] ptn107:
You can take the OTA if you want but to get back on LineageOS you will need to downgrade to stock MM first before flashing Lineage. The official nougat is 7.0 not even 7.1 so it wasn't worth it for me. LineageOS is 7.1.2 and up to date on security updates. Runs great with no issues. The link you provided is the correct download link.
[X Style (Pure) General] fayded:
Anyone know if it's possible to omit 'fastboot erase userdata' for a dirty flash as in the previous downgrade/OTA instructions before we got the full firmware release? I'm rooted on MM and can just Titanium backup and restore but would rather not if I don't need to. I can always clean flash if I'm having issues down the line
[X Style (Pure) General] twfs:
Hi just flashed all this successfully but I still have the bootloader unlocked message when the phone first starts up. I was hoping that would go away by flashing all the files pretty sure it did when I returned my g4 back to stock to sell it. So basically what do I need to get rid of the bootloader unlocked message or am I hosed since I did relock the bootloader thanks in advance. I went back in and flashed the logo.bin file that was in the zip and still couldn't get rid of it. So I downloaded the bin file by itself from the remove bootloader unlocked message thread and flashed it the same way and it worked. Can't believe it was bad in the zip because everything else flashed fine. The only thing I did do different was fastboot reboot afterwards instead of manually rebooting it.
[X Style (Pure) General] acejavelin:
It is supposed to show the Bootloader Unlocked warning screen any time your bootloader status is not 0... Motos have been that way for several years.

0 - stock/never unlocked

1 - Engineering Bootloader (should never see this in a production device, but will display unlocked bootloader warning)

2 - Relocked (will still display unlocked bootloader warning)

3 - Unlocked (will display unlocked bootloader warning)

It is not possible to return a device to a bootloader state of 0.

You can flash the logo.img with a locked bootloader to cover it, but remember that any future update may over-write that and it will show up again.
[X Style (Pure) General] annoyingduck:
Yes, I do it all the time.
[X Style (Pure) General] Holymsophy:
Is there a way that someone could please make a flashable zip for the M8992_1255331.29.01.88.09R modem file? I had a "roaming indicator on" after switching sim cards, upgraded to Dirty Unicorns Nougat rom thinking it would fix it, but no dice and currently not where I can do fastboot flash.

Thanks
[X Style (Pure) General] henryrcp:
Thanks Acejavelin and Xda team, i follow the instructions and i can update my moto x pure xt1575 to android 7.0.

I fail to apply the instructions in exact order, i see one error, jump instruction in line 5, but i execute after 16, before 17.

follow next instruction and phone work.

1 fastboot oem lock begin (see notes below if not wanting to lock)

2 fastboot flash partition gpt.bin

3 fastboot flash bootloader bootloader.img

4 fastboot flash logo XT1575-logo-new-9-14-15.bin

5 fastboot flash boot boot.img

6 fastboot flash recovery recovery.img

7 fastboot flash system system.img_sparsechunk.0

8 fastboot flash system system.img_sparsechunk.1

9 fastboot flash system system.img_sparsechunk.2

10 fastboot flash system system.img_sparsechunk.3

11 fastboot flash system system.img_sparsechunk.4

12 fastboot flash system system.img_sparsechunk.5

13 fastboot flash system system.img_sparsechunk.6

14 fastboot flash system system.img_sparsechunk.7

15 fastboot flash system system.img_sparsechunk.8

16 fastboot flash system system.img_sparsechunk.9

17 fastboot flash modem NON-HLOS.bin

18 fastboot erase modemst1

19 fastboot erase modemst2

20 fastboot flash fsg fsg.mbn

21 fastboot flash bluetooth BTFM.bin

22 fastboot erase cache

23 fastboot erase userdata

24 fastboot erase customize

25 fastboot erase clogo

26 fastboot oem lock

27 fastboot reboot
[X Style (Pure) General] thepepperman:
Looking at flashing this in place of my current NPH25.200-15 build. Would my modified set of commands be acceptable?

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img I have a custom bootloader image to cover the unlocked bootloader message

fastboot flash logo logo.bin I have a custom Motorola startup image

fastboot flash boot boot.img

fastboot flash recovery recovery.img I'm using TWRP and want to retain this

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 will try a dirty flash, if problems arise I'll do a clean flash and restore using TitaniumBackup

fastboot erase customize

fastboot erase clogo

fastboot oem fb_mode_clear

fastboot reboot
[X Style (Pure) General] acejavelin:
No... This isn't "acceptable" and it will fail. You must flash the bootloader.img, you are confusing what is what, that is not a picture but the bootloader itself... The rest is probably ok but be ready to do the whole thing.

A custom logo.img is what stops the "Unlocked warning", but you will lose your startup animation as that is in boot partition and it will be erased.

I am guessing your rooted to? Honestly, I would just flash thing, flash TWRP and re-root. Probably be less hassle.
[X Style (Pure) General] thepepperman:
Ok, appreciate the guidance. Rather do that than screw up and face more problems. Thanks!
[X Style (Pure) General] kpcurl:
Can I flash this through fastboot if I flashed a twrp backup of the 1575 nougat update?. I am still running the 6.0 modem firmware.
[X Style (Pure) General] dzidexx:
Yes, you can.
[X Style (Pure) General] Bysler:
Thanks to the OP for uploading this. I followed the instructions and successfully installed it without any hitch. I did make a batch file with the commands as it seemed a little bit tiresome execute each one by one.
[X Style (Pure) General] acejavelin:
Executing them one at a time is actually important... It is not uncommon for a single command to need to be repeated as it may fail the first time but work the second or even third time. Sounds like you just got lucky.
[X Style (Pure) General] Bysler:
I must have got lucky then :D. However, I have been flashing roms since the days of gingerbread and never once have had to execute twice a command. I assumed that the first time failing, it meant something wrong with the file.
[X Style (Pure) General] SoNic67:
I always use batch files and never had an issue, never had to give a command twice.

The logo can be changed later with one that covers the message, but the original is needed at flash time.

I have used a changed variant of batchfile that doesn't erase user data and it worked perfectly fine.