yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] dzidexx:
Logo is needed only for future ota's,

Stock Recovery will be installed by system with 1st boot,

Data, cache - must be erased when downgrading.

Very nice that you always succeed - so, maybe you can help here:

https://xdaforums.com/moto-x-style/help/rsd-lite-to-detect-moto-x-pure-t3717598
[X Style (Pure) General] nerdBrain:
For those having issues with VoLTE after flashing (at least on Verizon), I had to enter the hidden menu using *#*#4636#*#* and re-enable "VoLTE Provisioned" under the "Phone Information" menu.
[X Style (Pure) General] spainter:
I sideloaded the captured OTA on my xt-1575 a few weeks ago that updated it to NPH25.200-22 and it has been running great with no problems on Verizon. I woke up this morning to a notification of a 8 MB system update. I unrooted my phone and let it install the update. It finished successfully and updated the phone to NPH25.200-22-1 with a security patch date of October 1 2017, System version 25.201.1

I had no problem re rooting the phone and all seems to be gold.
[X Style (Pure) General] SoNic67:
My Verizon got the -23 version OTA (no sideload). I guess the 22-1 corrects what was wrong in the 22 that wasn't officialy accepted by VZW previously.
[X Style (Pure) General] autosurgeon:
The update is only the Oct security update to address KRACK. Nothing else changes.
[X Style (Pure) General] morvarid:
unlocked bootloader and update to android Nougat

hello , i have motp x pure with st0ck android 6.0 & unlocked boot loader & installed TWRP 3.1.1.0 on it.

how can i update to Stock MXP 7.0 Nougat ?

please help me
[X Style (Pure) General] dzidexx:
WTF?

In your post I see:

Answer

Question [MENTION=7708060]morvarid[/MENTION]
[X Style (Pure) General] morvarid:
its NOT flashable rom via TWRP
[X Style (Pure) General] dzidexx:
You cannot update to stock via twrp.

/Btw - you didn't ask for it/. [MENTION=7708060]morvarid[/MENTION]
[X Style (Pure) General] morvarid:
thanks for your answer but

do you know how i can update to stock 7.0 without loss unlocked boot loader ?
[X Style (Pure) General] dzidexx:
As I wrote - in your post are answers and question.

"Detailed instructions"

Link to:

"you are interested in returning to stock WITHOUT locking the bootloader, then follow the above commands, but the following commands in place of the "lock" commands in the list above:

fastboot oem fb_mode_set instead of fastboot oem lock begin

fastboot oem fb_mode_clear instead of fastboot oem lock"
[X Style (Pure) General] morvarid:
thanks
[X Style (Pure) General] abense:
Can I fast boot this from TWRP if i'm on MM?

I'm just kidding. Is there a way to theme this ROM (I haven't kept up with this stuff in about ~11 months.) or is there a good, stable, 'custom' ROM for this firmware that is themeable? I'm contemplating on whether to even bother upgrading from my MM pure nexus.
[X Style (Pure) General] autosurgeon:
Updating to 7.0 will not relock the bootloader and an unlocked bootloader will not effect the ability to receive ota updates as long as that is the only thing you have done to your device.
[X Style (Pure) General] acejavelin:
This thread is about factory firmware... No offense, but there are plenty of threads about what's a good custom ROM. The customization options on stock are the same as similar stock ROMs and it all depends what you want, now days for me all I need is Nova Launcher, a custom wallpaper, and maybe an icon pack, and that works fine.
[X Style (Pure) General] abense:
I was being somewhat facetious. (i know you can't run fastboot from twrp). -- Perhaps that joke was more humorous when I told it to myself than it actually was.

In all seriousness though; I flashed this firmware, however I've come to realize that I can't get 4G to work on the 12/13/2017 AICP build.

Is there any ROM that uses an N radio that I can use substratum with?

If I flash back to an MM radio, can I later flash back up to an N radio?
[X Style (Pure) General] morvarid:
I install android 7.0 with your method on my moto x pure, and it works great but when restart it show the fastboot menu and i should press START bottom(in fastboot) to enter android OS agian ? is it solvable ?
[X Style (Pure) General] dzidexx:
Probably you forgot:

fastboot oem fb_mode_clear

[MENTION=7708060]morvarid[/MENTION]
[X Style (Pure) General] morvarid:
thanks for your help ...., its solved
[X Style (Pure) General] burnski:
Hey guys, i did all of the instructions in the OP, reboot the phone, select language, connect to wifi, then when i go to connect to my google account it says "This device was reset. To continue, sign in with the previously synced account". so i login with the account, and i get an error message "unable to login due to an unknown error".

any guesses?
[X Style (Pure) General] vance2804ibr:
Thanks for this thread. So is there a way to rid the unlocked bootloader image at the beginning?
[X Style (Pure) General] acejavelin:
Same as always, flash a patched logo.
[X Style (Pure) General] silver04v:
Does having the bootloader unlocked on our device cause the saftey net trip? I just got the latest OTA up to date, was going to unlock bootloader with moto and then fastboot install twrp and then flash MAGISK...

Is this going to give me a tripped safety net, and besides say, banking apps, and netflix, what is the real big deal with safety net? Anything?
[X Style (Pure) General] acejavelin:
Yes it does cause SafetyNet API to fail... But Magisk can hide that.
[X Style (Pure) General] silver04v:
ahh, I wasnt aware of that. Been away to long and I've been trying to read everything catching up.

So there's no real risk at the moment, except for the standard known ones in rooting, etc.

Do my steps appear correct in moving forward?
[X Style (Pure) General] aybarrap1:
Yes they are correct. And as mentioned, Magisk can mask an unlocked bootloader from safety net. Just make sure you keep it updated because Google does update the safety net sometimes and the Magisk dev has to do his magic to keep Magisk working.
[X Style (Pure) General] Bill720:
Hypothetical question

Just out of curiosity, what would be the most likely outcome if I installed this (200-22) over 200-23?
[X Style (Pure) General] annoyingduck:
Should work fine. I downgraded from -25 to -22 without issue and took the -25 OTA to clean up my device. No problems.
[X Style (Pure) General] hometech99:
Thanks for this.

After glitchy custom roms and so-so battery, this has been great... smooth, fast, and my battery lasts from 5:45a till 9p.... usually had to charge at 2pm on latest aicp.
[X Style (Pure) General] fathergweedo:
I've been away for quite awhile myself. Hadn't even heard of Magisk until recently :o. Planning to flash this (Nougat) as soon as I have all of my ducks in a row, but will keep the unlocked bootloader as I need root. The fastboot procedure will overwrite my custom recovery (currently TWRP 3.0.2-0) so I'll need to reflash it in order to install the Magisk.zip. Pretty sure I have all of this down but am curious what version of TWRP people are using/have verified working. Might I safely assume the latest (twrp-3.2.1-0-clark.img) will do the trick?
[X Style (Pure) General] silver04v:
yessir

Using the newest on TWRPs site for the clark XT1575..

Flashed magisk, set it all up, learning curve but there is plenty of information on here about it all. It comes back to you once you're in it.
[X Style (Pure) General] fathergweedo:
Thanks for the confirmation. I have another one of these coming in a few days for the wife so I'll do the deed on that one first. Then I'll know if I like nougat enough to flash mine. Files are all on the laptop and ready to go :thumbup:
[X Style (Pure) General] Optimusman:
Hey I just wanted to drop in and say everything worked perfect! Updated to October security patch and nougat. Thanks for the firmware package and directions.
[X Style (Pure) General] mi6300m:
I can't lock my bootloader with this unfortunately, I took the OTA about 3 weeks ago. And a day or so I unlocked it to give LOS a try again, and when I later found out that I needed to downgrade the modem I aborted and tried to go back to stock. Now when i try it says this file isn't a signed image and I get "preflash validation failed" errors on the GPT, Boot, Systemchunk files.

I doubt there's anything that can be done to lock the bootloader again. If so, any help would be appreciated. Otherwise there goes my G-Pay...again. lol
[X Style (Pure) General] acejavelin:
Nope... nothing that can be done until we get a newer factory image. Sorry.
[X Style (Pure) General] allaindungo:
I have the same problem. I was about to lose hope because the Restore function in TWRP is not working. Tried to flash again and same errors preflash. Finish it and did not boot. Tried the restore function and I was shock it boots in animation.
[X Style (Pure) General] stevejohnson42:
Finally had a chance to do this - NICE !

I only stayed on it for a few minutes - enough to find that the Fly Delta worked on it - then moved on to NucleaROM ; well - at least for a bit.

There have been a number of Nougat ROMs compiled by [MENTION=4950398]andreskafe[/MENTION] that use the stock N modem ; best I can tell - this thread is the best way to get on that. I have only tried his NucleaROM - but ; there are choices if the N stock had been on the device

Nice to see some love for clark --

Thanks for getting this out there -- solved the one nagging issue that kept me on MM
[X Style (Pure) General] wiseguyy:
I have a question, my son needs a phone to work for VZ so would I flash (this) N to this phone and since he is on Verizon his device will then get an update / OTA to NPH25.200-23 because he is on Verizon? I looked for that specific factory image but I can't seem to find it. If not... am I correct that this image is the best I can get for this device at this time regardless of the network the device runs on?
[X Style (Pure) General] StankFiss:
There are 2 releases nougat for x1575. 25.200.23 and 25.200.22 with minimal differences. I'm on 25.200.22 then updated to 25.211.1 and on Verizon with no issues. This is the only firmware for the x1575 that is available. With that being said , with this firmware you can re-lock bootloader or revert back to this firmware. You cannot do that at the moment with 25.200.23 that I know of.
[X Style (Pure) General] wiseguyy:
Moto X Pure Firmaare

Well I need to flash factory firmware so 25.211.1 is latest Verizon where can I get that to flash to this device. OEM firmware right ? ...because my son is on Verizon?
[X Style (Pure) General] StankFiss:
yes 25.211.1 is latest MOTO X PURE update. This has nothing to do with any mobile carrier update. Before you do make sure you fully understand the steps on how to...... Once you install any nougat firmware you CANNOT go back to marshmallow.
[X Style (Pure) General] wiseguyy:
OK....wait .....since this device is on 6.0 then I need to flash the Stock Nougat firmware then go from there ...Right..and I have looked for the (25.211.1) your talking about and I find no stock official firmware to flash??
[X Style (Pure) General] jweaks:
Confused... I'm on Verizon and running 25.200-22. Is it okay to take the OTA update?

I'm not sure if my phone is just crapping out on me or it doesn't like the firmware. It ran great for about 2-3 days after I moved to 25.200-22 and it's been bad ever since. Poor battery life, crashing, inability to use multiple apps without freezing, running hot to the touch, etc.... The install was clean and I've wiped 3 or 4 times since to see if that would help. It didn't.
[X Style (Pure) General] hometech99:
Just want to be sure...

If you were on MM and took 7.0 OTA, and then flash this full 7.0 image in fastboot

then flash MM - based ROM, and /or go back to stock MM and take OTA again, it won't brick this time?
[X Style (Pure) General] HonestOtter:
I want to try the stock rom. I am currently on an old version of AICP 7.1.2

I still want root.

Can I do this with this method?

would i just use "fastboot oem fb_mode_clear" for the 2nd to last command?

Any help or suggestions appreciated.
[X Style (Pure) General] acejavelin:
Yes, it will... Once you are in an official Nougat firmware including GPT and Bootloader, if you downgrade to Marshmallow, then try to OTA back to Nougat... It's bricksville.
[X Style (Pure) General] acejavelin:
Change 1st and 2nd to last commands as noted and your good.
[X Style (Pure) General] hometech99:
Ok...but if you go back to 7 by using this full firmware--will you get security/feature OTA updates, because taking original OTA told servers you have 7.0?
[X Style (Pure) General] hometech99:
Well that's a no...no OTA loads to this because of its 22 version. The 23 OTA only loads to 16 MM, and the newer 211 OTA will only load to the 23.

So this "official" firmware leaves you stuck here with no security updates.

Might as well do custom ROM on N modem instead.
[X Style (Pure) General] annoyingduck:
That's wrong. If you full flash 22, you will get the 23 OTA. I've done it twice with a Verizon sim. Works fine. I also have the 23 OTA linked in 2 threads to sideload from 22 if your not getting the OTA notification.
[X Style (Pure) General] stevejohnson42:
I had the same observation / results -
[X Style (Pure) General] hometech99:
Thats not wrong....I have 2 phones now on this full 22...neither get the 23 OTA, and trying to ADB it gives me keys errors and aborts. Im leaving our 3rd XT1575 on MM until this works so I don't have 3 phones now stuck in 7 land and unable to lock the bootloader.

The 23 ota expects 24.49.18-18/8 or 25.200-23/22.

What do YOU show as version after flash full 22 as in About Phone, or in stock recovery top of page?
[X Style (Pure) General] annoyingduck:
Don't know, not on 22. But I just did it a month ago flashing the full 22 package here and immediately got the OTA to 23. The 23 OTA file I pulled was pulled when I was on 22. I'm not the only one either, your the first I've heard of being locked in on 22. Sounds like maybe something isn't flashing correctly in your devices causing the update to fail. I use Linux (adb binaries are always current), is your adb up to date? Only thing I can think of.
[X Style (Pure) General] hometech99:
Well, that contradicts this early comment by acejavelin in November:

"The issue is we know the Moto OTA server keeps track of what device get's what version, if you flash this (full 22 listed here) it won't know you have it so if a future OTA update comes out..."

That totally messed me up because it led us to take the OTA, so the server would know we have it, then tried to flash this full version to relock the bootloader..which of course wont flash completely because of the A0.52 bootloader.

We are left with this 25.200.22-1 build with A0.52 BL which none of the 2 OTA will go over (no OTA offered, and key errors if try to ADB the OTA people provided) , and preflash validation still if try to flash full 7.
[X Style (Pure) General] StankFiss:
False statement. This firmware will lead to the last update which is 25.211.1.
[X Style (Pure) General] hometech99:
Well, thats not a helpful statement; more of a personal attack. Is that allowed?

So my phone is a liar then? I'm only reporting what it is telling me....If OTA was downloading/ADB flashing, would I be posting here?

How about something more constructive?
[X Style (Pure) General] StankFiss:
No you made a blanket statement saying all phones will not update after using the firmware. Wanted to make clear that it does let you update.
[X Style (Pure) General] Hitti2:
I am on NPH25.200.22 and receiving an ota update notification. I tried twice to upgrade but on bootup I get error. Hold power button 10 seconds power off and on then when phone boots into nougat, it states update failed.

What am I doing wrong?

Thank you.
[X Style (Pure) General] Hitti2:
I had to go through the install process again but with locking the bootloader. OTA 25.200.22-1 went through!
[X Style (Pure) General] stej16:
do i have to lock the bootloader during flash (and then unlock) to install twrp? i didn't n i'm having a problem installing twrp.. it says it installed but it didn't. install time was too fast too. i've had this problem in the pasted but can't remember how i fixed it

also: after flashing 25.200.22, with no sim card i get update 25.201.1 - which i did not install cuz not sure since ppl are reporting i need to lock the bootloader at flash. is this confirmed?

edit: custom recovery fixed. had to power off instead of reboot.
[X Style (Pure) General] hometech99:
Well, blanket for what is happening on my phones.

What am I reading now in these later posts---does the bootloader have to be locked on this full firmware to get the 2 laters OTAs?

That could be my issue....I cant lock because of this A0.52 BL from the OTA before.

So, even flashing this full firmware with no lock becasue gpt fails, does not let me ADB the 23 OTA it seems...

Have we ever had to have bootloader relocked to get an OTA??
[X Style (Pure) General] stevejohnson42:
I had one security update after updating with the files.. I never relocked the bootloader

Can't comment on second update , I had stock installed for maybe 10 minutes before I installed twrp and put on a custom rom
[X Style (Pure) General] ipulaski:
havent read all the pages, i am still on Moto XT1575 Marshmallow, how can I upgrade to Nougat without rooting>
[X Style (Pure) General] stevejohnson42:
First suggestion - read all the pages and also the links in the OP

Also review this thread - https://xdaforums.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808

To the best of my knowledge you can use the instructions in the OP ( follow the links too ) you can -- this is done through ADB ; you wouldn't need root . Fastboot needs to be working / set up
[X Style (Pure) General] smithmal:
Flash of firmware went fine. Thanks OP! Just tried installing official update and now my phone will constantly boot to TWRP. How do I fix this?

Thanks,

Smithmal
[X Style (Pure) General] jason2678:
Wipe cache
[X Style (Pure) General] acejavelin:
Wipe cache and don't take update again... OTAs require stock recovery and system partition.
[X Style (Pure) General] smithmal:
Thanks for your response. I preformed a "Factory Reset" wipe in TWRP (wipes data, cache and dalvik) but that didn't work. I was able to fix the issue by booting into the stock Bootloader (either through TWRP or by holding POW + Vol Down buttons once the phone is shutdown) and selecting "Factory" to reset the phone to factory settings. From there, I was able to get my phone to boot normally. I then rebooted back into TWRP and re-installed my backup.

According to information @ XDA, the easiest way to get rid of the constant OTA reminder prompts are to ignore them. Within 6-7 days of ignoring the prompt, the Moto Update Services will stop reminding you altogether.

Thank,

smithmal
[X Style (Pure) General] acejavelin:
That's weird... Wiping cache(s) only in TWRP has always worked in the past with just about every phone, and definitely all Moto devices in the past several years, a factory reset has never been necessary that we have seen. Glad you got it working!
[X Style (Pure) General] kb8no:
I have been on MM firmware and was using Hashbang LOS14.1 Official. So I used this to upgrade to Stock N on N firmware. I now use LOS14.1 Unofficial which is N Firmware based. Hashbang says on N Firmware the M TWRP has problems with wiping and bootloop. He made a N TWRP that fixed that problem. Only the M TWRP is on the TWRP site. Hashbang should know as he us the MotoXPure TWRP maintainer. The LOS14.1 Official site is where you find the links to the Unofficial. I linked Hashbang N TWRP above. This is what you should use on N Firmware. LOS8 will be only N Firmware. He has working builds that are promising. When he starts mainstreaming O I expect he will offer both N and M versions. If you are bootlooping try the Unofficial TWRP.
[X Style (Pure) General] MotoDudeX:
Ok I'm stumped. Hopefully someone might be able shed some light.

Followed the original instructions to a T - everything flashed "Okay" (including the NON-HLOS that took two times) - booted right up and for whatever reason, I have trouble with connectivity.

On initial bootup, without changing any settings, it shows I have LTE and verified it worked. Tried to check my voicemail - "mobile network not available" or "Cellular network not available for voice calls" - Checked my APN settings, everything looks good. Everything was working fine previously on TruPureXMM 2.9

Tried doing the *#*#4636#*#* - changed the band to United States, same deal. LTE data works fine but under voice service it's showing "Emergency calls only"

Tried adjusting the "Set Preferred Network Type"

US Band

LTE/CDMA Auto = Emergency Calls Only / LTE

LTE/CDMA/UMTS Auto = Emergecny Calls Only / LTE

CDMA Auto = Emergency Calls Only / LTE

CDMA Only = Emergency Calls Only / LTE

Cellular 800

LTE/CDMA Auto = 1xRTT Voice / EvDo-rev.A

LTE/CDMA/UMTS Auto = 1xRTT Voice / EvDo-rev.A

CDMA Auto = 1xRTT Voice / 1xRTT Data

CDMA Only = 1x RTT Voice / EvDo-rev.A

Class 10 (800Mhz-Secondary)

LTE/CDMA Auto = Emergency Calls Only / LTE

LTE/CDMA/UMTS Auto = Emergency Calls Only / LTE

CDMA Auto = Emergency Calls Only / LTE

CDMA Only = Emergency Calls Only / LTE

PCS

LTE/CDMA Auto = Emergency Calls Only / LTE

LTE/CDMA/UMTS Auto = Emergency Calls Only / LTE

CDMA Auto = Emergency Calls Only / LTE

CDMA / Only = Emergency Calls Only / LTE

Then I went on to try to see if a custom rom would work. Flashed unoffical TWRP from hashbang - no problems during installation. Installed Unofficial LineageOS 14.1 from Hashbang and then tried NucleaROM (to see if that'd make any difference) - still had the same issue across roms.

In the US on Straight Talk (on Verizon's Network) sitting on stock from the original post, no custom recovery

Baseband

M8992_1255331.29.91.88.09R SUPER_NA

Kernel

3.10.84-perf-ge617f58

hudsoncm@ilclbld26 #1

Tue Aug 29 00:53:54 CDT 2017

System version

25.11.22

Build Number

NPH25.200-22
[X Style (Pure) General] acejavelin:
This sounds like a SIM or carrier issue... It your IMEI went to zero. Can you try your SIM in another phone?
[X Style (Pure) General] MotoDudeX:
Hey Ace!

I'll see if I can scrape up another phone I can drop this SIM into. What exactly would I be looking for once I did do that?

Everything was working just fine on Marshmallow the day before I flashed this file (Voice+LTE) - then it all went down hill. Right now I've settled with 3G w/ Voice on the current setup and it's OK (incoming/outgoing calls and texts work, slow internet) but not having LTE is a bit of a bummer. I can get LTE working but then I lose voice altogether and that's not worth it.

Just let me know what you'd like me to try and what I need to take note of and I'll do it!
[X Style (Pure) General] acejavelin:
Just to make sure the SIM works... But I don't think that's the issue after I read some more.

This really sounds like your kernel and radio are mismatched, I would reflash all radio images (fsg.mbn & non-hlos.bin) and the boot image and start there.
[X Style (Pure) General] MotoDudeX:
Is there anything outside of your original post that you are suggesting?

I tried the process in the original post a few more times and I verified everything said "OKAY" before proceeding to the next part of the flash until the end, did the reboot and still have the same issue.

I went back and double checked that the hash of the file I downloaded matched up - it did.

The only time I had an issue similar to this in the past (with other devices) - there was a supplementary "modem fix" zip I needed to flash and that ended up getting me up and running - so I definitely think you're right about what the issue is - I just don't know what to do :(
[X Style (Pure) General] acejavelin:
Sorry, I got nothing... Literally dozens if users have used this process and file without any issues. It is an "official", digitally signed factory image.

I don't recall ever seeing a "modem fix" zip for this device, except when you had to downgrade radios for certain custom ROMs.

Maybe go through the XML file in the zip to see if your missing a step? It's reaching but I don't know what else to try.