yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] ParkyTech:
Huh, Well alright! I just saw something about the december update (which XDA refuses to let me post the link here) and was concerned as to why I only received 1 update after flashing back to the may update, since when I first received the phone yesterday it did 4 updates I believe. It might've been a really old version, but good to know it's up to date!
[X Style (Pure) Android Development] quakeaz:
Yep, the release notes are out there. Nobody knows why the update is not available. Probably the same reason we just got the September 2016 patch in January 2017 if I had to guess.

https://mobilesupport.lenovo.com/us...-Series/Moto-X-Pure-Edition/Solution/MF116158
[X Style (Pure) Android Development] Hemidrosis:
Bumping due to the discovery of the latest stock Sept. firmware for XT1575

https://androidfilehost.com/?fid=745425885120703327
[X Style (Pure) Android Development] OldBaldy:
Flash of gpt failed,. This usually indicates you're trying to flash an earlier version of software than what already is on the phone. I would try flashing the latest version which is located a post or two above yours.
[X Style (Pure) Android Development] Motoven:
I am trying to do it with the most updated image that Lenovo gives me, and I still have the same error, I really do not know what to do.

i Try with CLARK _RETUS_6.0_MPHS24.49-18-18_cid9_subsidy-DEFAULT_CFC and the same error
[X Style (Pure) Android Development] OldBaldy:
That is a mislabeled file. It's actually the same as CLARK _RETUS_6.0_MPHS24.49-18-3_cid9_subsidy-DEFAULT_CFC*

The latest is CLARK _RETUS_6.0_MPHS24.49-18-9_cid9_subsidy-DEFAULT_CFC*and is available from the filehost link in the post directly above your original post. It's the same release as the latest OTA and is what I'm running.
[X Style (Pure) Android Development] Asturie:
Currently using TruPure Rom which uses system root. I'm interested in going to LineageOS and using magisk systemless root. To remove all the system root traces is flashing the 6.0 MPH24.49-18-3 Stock Unrooted TWRP Backup and doing a standard wipe good enough or do I need to go back to stock completely?
[X Style (Pure) Android Development] pizza_pablo:
The "latest" on Moto site, dated September 2016 is actually the November 2015 security patch version.
[X Style (Pure) Android Development] pizza_pablo:
I know because I am currently running it, from that source.
[X Style (Pure) Android Development] smvb64:
Hey, just want to verify something quick.

I was updating my moto x pure version 18-3 to 18-4 via flashing the firmware with fastboot, following the instructions on page 19.

The flashing process went smoothly but I kept getting these type of message before every flash.

(bootloader) has-slot: partition: not found

(bootloader) has-slot:logo: not found etc

Is this an issue? the phone is working correctly

Thanks SM
[X Style (Pure) Android Development] Sgt-P1:
flash stock 5.1.1 from 6.0

is is possible to flash 5.1.1 on the 6.0 mphs24.49-18-4 build>?

a downgrade? that would work?
[X Style (Pure) Android Development] CLETjB:
MPHS24.49-18-16 is the December 1, 2016 security update, just came out last week.
[X Style (Pure) Android Development] chromatica86:
Does anyone have the December update to flash via fastboot? Trying to return to stock to sell. I had the update installed, then unlocked again and went to lineage.
[X Style (Pure) Android Development] ParkyTech:
I'm wondering the exact same thing. I'm unable to receive the update. It doesn't come through so I want to flash it via fastboot mode. I could do it from the package that was pushed out, but I don't want to do that until I have the December firmware
[X Style (Pure) Android Development] SLIP76:
MPHS24.49-18-16 caused Bluetooth issues in my case. Looking for downgrade.
[X Style (Pure) Android Development] ffejy462:
Been using Bluetooth all day with no problems.

---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------

https://xdaforums.com/moto-x-style/...llow-6-0-september-2016-t3536120/post71169193

You could always just flash stock recovery after...
[X Style (Pure) Android Development] ParkyTech:
https://xdaforums.com/moto-x-style/...llow-6-0-september-2016-t3536120/post71169193

You could always just flash stock recovery after...[/QUOTE]

I'd rather not until the stock firmware comes out. I want to be able to flash back to complete stock and relock the bootloader before I apply the update. I can't do that when the only valid partition file is from september.
[X Style (Pure) Android Development] ffejy462:
I flashed the may complete stock firmware and took the two updates. There no need to relock the bootloader to update. I wouldn't relock unless you're going to sell.
[X Style (Pure) Android Development] kitcostantino:
nice avatar. best album ever.
[X Style (Pure) Android Development] SLIP76:
Spent whole Sunday backing up -> downgrading -> restoring. Tested bluetooth with my car's infotainment system today - everything works fine - just like before upgrade.

Had to unlock bootloader via Moto website - fortunately it was fast enough.

The problem with Bluetooth was (if anyone interested or will find this post) - the phone connects to car system but when trying to make a call - car system displays message - call failed while the call is actually active on phone in a pocket... Also Bluetooth-related processes drain battery almost to zero during a half of the day (when I'm in the office/home - car is definitely too far to establish connection).
[X Style (Pure) Android Development] eigerzoom:
battery life on latest december upgrade is considerably worse than ever before on this device

maybe i'm forgetting some system apk's to freeze in titanium that i had before

anyone else?
[X Style (Pure) Android Development] CLETjB:
I agree, but I abiding my time for Nougat to be released (Hopefully by summer).. If at all
[X Style (Pure) Android Development] eigerzoom:
I can only guess nougat will be even worse on battery life
[X Style (Pure) Android Development] aj_deuerling:
I used this coming from TruPure 2.6 (Android 6.0) and TWRP using the 6.0 MPH24.49-18-4 FIRMWARE and the batch file to run through it all. After I rebooted, it said there was a 24.221.8.en.US update and when trying to install it, it fails and errors out. I have not re-locked my bootloader yet, is that the issue? I have read that it wouldn't cause this, but I am unsure of what else could.
[X Style (Pure) Android Development] Ohmster:
Me too. I did the OTA on a rooted Moto X Pure XT1575 which is a bit of a hassle when the device is rooted with Xposed. But I have done this before and did this one correctly. Everything worked just fine after the update. I made a backup of my working system before attempting any sort of update or system change with TWRP on 2/20/2017. Then I made my clean system partition on 2/2/21/2017 and did the update with FlashFire to preserve root and what a good job it does at that! I used the Xposed framework apk to reinstall the Xposed framework and had all of my Xposed modules back. Nice, no issues.

I use Bluetooth every day, either on my Plantronics headset or my Belkin car audio system. I started having problems with it days ago, having to unpair and then repair the connections, reboot, or wipe cache and ART. All of this would work but not for very long. Within a day or couple of days, not working again. Now it connects with (no media) and is totally useless! That security patch is useless to me but Bluetooth is not. I want the update gone and my Bluetooth back. Fortunately I have a backup to restore from before the actual OTA and am getting ready to restore it now. In process of copying it from my PC storage back to the SDCard. I am using a dual headed USB flash drive and could just have easily restored the backup from there, but want the backup on the device in the event I need it more than once. If that fails for whatever reason, I will use the Clark firmware package to restore the system back to where it was before the OTA. The packager of the Clark zip firmware file included a wonderful batch file That would restore the system and not touch your data at all. Works very nice.

There is a lot of talk about this issue on the net but so far, no confirmed fix for it. So for me, it is time to downgrade. I hope that someone finds a genuine fix for this but I am just hoping that Google knows about it, will fix it, and that fixed version will be in the next OTA for Moto X Pure owners. Best wishes guys! :p
[X Style (Pure) Android Development] quakeaz:
Did you try turning off Bluetooth scanning in Location Settings?
[X Style (Pure) Android Development] Ohmster:
What does that mean? I just restored a TWRP backup from before the system update and am waiting for the app count to finish and see if it worked. So I am unable to look in my phone right now to see what you are talking about. Can you elaborate a bit more please? Thank you. :confused:
[X Style (Pure) Android Development] quakeaz:
See this thread / post:

https://xdaforums.com/moto-x-style/...vity-issue-t3555490/post71027630#post71027630

Settings > Location > 3 dot menu > Scanning
[X Style (Pure) Android Development] eigerzoom:
you can just flash the BTFM.bin from the firmware files of a previous release....you dont have to downgrade everything just to restore bluetooth functionality

you might need to be rooted though, i'm not 100% sure, maybe someone else can confirm

i've done this before when I had bluetooth failure after an update, though the latest update is working fine for me in the bluetooth department

you might want to just try reflashing the latest BTFM.bin from the latest update zip thats linked here on xda before trying an older version since it is working for most people
[X Style (Pure) Android Development] quakeaz:
Or you can turn off a simple setting within the OS... ;)
[X Style (Pure) Android Development] eigerzoom:
I assumed that people were still having issues even after setting the scanning

i've always shut that off, bluetooth scanning is just for googles and the governments data mining / human behavior efforts

i do recall a time when shutting it off though made maps stop working properly, i use to get so angry, like really google, you are gonna force me to tell you about everything within range of my device, please fock off
[X Style (Pure) Android Development] quakeaz:
I can't speak for all, but it has worked flawlessly for me after disabling BT scanning, and apparently a few others in the original thread that was created after this problem was introduced with the September OTA.
[X Style (Pure) Android Development] Ohmster:
For the record, quakeaz advice probably works quite well:

Settings > Location > 3 dot menu > Scanning OFF

I downgraded from the 12/1/2016 security update back to 9/1/2016. That took ALL of my Bluetooth problems away. But had I known about this option, I would for sure have tried it first. I posted screenshots of the scanning switches and my About Phone so you can see what version I am at now and very happy about it.

Okay I saw the post to go into Location and turn off Bluetooth scanning. I wish I could look now but I just restored a pre update backup and am waiting for the app count to finish so I can boot. In the Bluetooth menu, scanning for devices times out really quick, the 3 dot menu will allow a refresh to pickup a device you wish to pair. I know that WiFi does scan since I am getting statusbar messages when I go out that WiFi networks are available, but had no idea or clue that Bluetooth would do anything similar. Why, what for? You can hook on to public WiFi but so far as I know, there are no public Bluetooth broadcasting to access. It is more of a phone to phone thing or to connect stuff like speakers, keyboard, or whatever. This is very interesting and if true, poses yet another dilemma. Do I restore my updated TWRP backup again or just leave it for the next OTA, by which time Google should have addressed this issue. Updating 222 out of 229 so it will not be long to have a look at what you are talking about. This is something I definitely want to see!

Ahh, there is the bootup sound, waiting on desktop to fill out and sync up the widgets. Holy crap, there is a setting for WiFi AND Bluetooth scanning and of course, they are both turned on. Screenshot attached. I wonder if that would have solved the issue? Too late to try it now but not too late to see if my Bluetooth works or not, trying now. Headset works perfect. Now for the car. Paired quite nicely, works perfectly.

Well, I think we nailed it, the December 1st security OTA patch was a Bluetooth killer. My phone is working perfectly now and I am not exactly out of the game with the September security patch in place. I did shut off Bluetooth Scanning in Location as suggested and am deliriously happy now, thank you! Will I restore my 12/1/2017 security patch update in TWRP? I dunno. Not now at 2:30 AM, that is for sure, but my curiosity is now piqued and I might just do it if I have the time and am bored.

Thank you very much [MENTION=5284599]quakeaz[/MENTION], I can now sleep peacefully as this really is my ONLY phone and I depend on it so much. If I do the restore and test, I will be sure to post them here. Good night! :highfive:
[X Style (Pure) Android Development] Ohmster:
I have the December 1st update, got it from OTA. It broke Bluetooth and I need and use Bluetooth every day. The issue did not show up right away, I used the phone as usual, the only thing I did different was to shut off auto updates from the play store since there were so many of them, constantly, I was not comfortable giving every app carte blanche to update itself. Within 2 weeks, I started having Bluetooth issues. Not connected, reconnect. Connected but with no media, useless for any purpose. I could get it working again with either a reboot, or a system wipe of cache and ART/dalvik, then it would work again, but not for long.

There was a post to use the Settings menu and reset the network, you lose your WiFi passwords and connections. I did this, got back on WiFi, and tried my Bluetooth again. NO improvement. I would rather have a working phone with reliable Bluetooth than a security patch that does more harm than good so I am currently trying to restore a TWRP backup, pre-system update. I did not restore Data since I want to keep all of my apps, passwords, text and messages,etc. Rebooting now and waiting on the app count. I will wait and post the results since I took you this far, might as well give you the results. 140 out of 229, this will take a while.

Everything works fine, Bluetooth is like new again and I am now at the September 1st security patch and not the December 1st one that gave me all this trouble. [MENTION=5284599]quakeaz[/MENTION] really saved the day by revealing some hidden settings that affect this, I turned them both OFF when I found out about them and you can see my results and his advice here if you would like to see how this worked out.

https://xdaforums.com/showpost.php?p=71506050&postcount=342

I am very happy. :D 'night guys!
[X Style (Pure) Android Development] Tumbtack:
OTA updating just returns a screen with the android on its back with the text "Error!" under it. Yes, I removed TWRP and flashed the marshmallow recovery.
[X Style (Pure) Android Development] tech_infinity:
[MENTION=5938234]Tumbtack[/MENTION] if you already had say September security update, then you flash a custom rom. Then you flash an older version of stock rom. Then you try to update that's when you get this error. You need to flash the latest version of stock rom that you ever used.
[X Style (Pure) Android Development] annoyingduck:
I fastboot flashed the latest May image and ota'd to the current December build (ends in 16) to prepare for 7.0 - worked great. It should be noted in the "useful commands" section that the Bluetooth partition command is missing, so you need to remember to do that (the command is noted in the September build directions).

I needed root to restore my apps & data for my apps. What I did was to live boot TWRP via fastboot being sure to select the read only option upon boot (live booting keeps stock recovery) and I flashed the latest sr3 SuperSU (which installs systemless by default WITHOUT having to enter the command that the stable release requires). Worked perfect. So now I'm stock, systemless rooted, with the stock recovery.

Now how should I ota to 7.0? Remove root, or just let the ota install and see what happens? Is there any reason that the ota would fail seeing as I'm full systemless without TWRP actually installed?
[X Style (Pure) Android Development] eigerzoom:
I brought up stock before rooting and nearly instantly got the notification for system update.

I would start over and just boot into stock before rooting if you aren't getting the update notification or if manual update fails.
[X Style (Pure) Android Development] gokart2:
Nobody has the nougat soak test? Seems like FOREVER now. Wish it was like the old Motorola, first to update....
[X Style (Pure) Android Development] Hemidrosis:
Select people have it, but chances are these people are just your average joes that don't know how to capture an OTA.
[X Style (Pure) Android Development] MedzHovig:
The Bat file worked like a charm... However, I now have no recovery.. looking to put the stock recovery (3e) back on the device and my bootloader code will not go back to code 2

I flashed the most recent moto provided image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml

I'm on a XT1575

Any thought on how to put the stock recovery back on?
[X Style (Pure) Android Development] pizza_pablo:
It seems like you wouldn't want what's out there.

https://xdaforums.com/moto-x-style/general/moto-x-pure-edition-official-android-7-t3596712/page22
[X Style (Pure) Android Development] gokart2:
I would actually. Only issue I see is the volte, which means nothing to me and could be fixed later on if needed.
[X Style (Pure) Android Development] pizza_pablo:
I guess you missed Moto Guy's posts about his unusable phone. That is enough to keep me on the sidelines for a while.
[X Style (Pure) Android Development] gokart2:
I did miss that, but was he the only guy?
[X Style (Pure) Android Development] pizza_pablo:
That was the most serious issue, there are others, I think more serious than no volte. Sure it may get straightened out, prior to release, I just wouldn't want to be trying out a dl of the soak test, but that's me, you may be an Android dare devil. :cowboy:
[X Style (Pure) Android Development] gokart2:
Yes and no on the daredevil-ness...lol. Although I've put myself in a few bad positions, I've typically been able to get out of most. But your probably right. Now that I think about it, don't really remember any soaks that were bad? Just been forever it seems. Starting to want a new phone.
[X Style (Pure) Android Development] pizza_pablo:
I recently found that the ZTE Axon 7 has CDMA capability (I'm on VZW) and got excited that there may be another choice, but after some research, it looks like big red doesn't let it function completely on their service.

Then I started comparing the G4 Plus & G5 Plus. Out of the two would prob go with the newer.

I've always preferred Motorola for their strong radios, but since Lenovo bought them, so knows if that level would continue. Prob not.

Why no new Nexus?

Not many choices.
[X Style (Pure) Android Development] gokart2:
I agree, nothing has really tickled my fancy though. Was thinking LG V20 if it's unlockable, if not then the HTC 10...if that's unlockable...lol. Want the LG for it's DAC's. Got a new car with a kick-ass audio system, and been a audiophile for awhile now.
[X Style (Pure) Android Development] pizza_pablo:
Started with a 64GB MXPE on December 2016 security patch and apparently I did something dumb....

After unlocking bootloader and flashing TWRP I attempted to backup a nandroid. It told me that it couldn't mount data, so I find a tip on the interwebs and followed it...

TWRP advance wipe - DATA - REPAIR OR CHANGE FILE SYSTEM - CHANGE FILE SYSTEM - EXT4.

After making the nandroid I attempted to reboot system. Bootloops between unlocked bootloader warning screen and TWRP (screenshot attached).

Tried erasing and reflashing TWRP. I can get to TWRP, but no success with restoring the nandroid.

Don't know what to do next.
[X Style (Pure) Android Development] pizza_pablo:
Ok, I got it to boot system.... After....

Fastboot erasing cache, fastboot erasing recovery, fastboot flashing twrp, starting twrp recovery, formatting data, factory reset, boot system.

Well, the boot animation seems to be taking a long while, but I'm better off, I guess...
[X Style (Pure) Android Development] ffejy462:
The stock data partition is f2fs. You're going to want to check and change it back.
[X Style (Pure) Android Development] pizza_pablo:
Thanks, I don't think that's one of the six choices.

Is it referred to as something else?

ETA, that WAS the last choice! Thanks!

I did that, formatted data and factory reset.

Here we go...
[X Style (Pure) Android Development] pizza_pablo:
Still stuck at boot animation, but I can get to bootloader and TWRP.

I tried the following :

Format data

Factory reset

Repair data

and combinations of.

I believe I am sunk until the firmware for December 2016 becomes available.

Is there any piece of available firmware that I could flash or must it be the entire December 2016 firmware?
[X Style (Pure) Android Development] ffejy462:
https://xdaforums.com/moto-x-style/...llow-6-0-september-2016-t3536120/post71169193

Since you were already on December patch, this should work.

Wipe data, system, cache, and dalvik.

Make sure data partition is f2fs. The others are ext4.

Restore system and boot from link.

Reboot

I'd wait to flash SuperSU or anything else until you have a successful boot.
[X Style (Pure) Android Development] pizza_pablo:
So, the Google Drive link on your post from 24 February, is the December 2016 firmware?

Cool, but what's up with Bluetooth?

Can I just flash the part, for data partition, that I messed up? What commands would that be?

What do you mean by, 'restore system and boot from link'?

Why hasn't it been added to the OP of this thread?
[X Style (Pure) Android Development] ffejy462:
Yes. Completely stock December system and boot twrp backups.

The Bluetooth issue was a small, but annoying thing. Bluetooth would turn off during reboot, but I believe that you can change that by turning off bluetooth always scanning in settings.

I don't maintain this thread. The drive download was just something I did after I couldn't find the firmware in its entirety so I flashed the an earlier release and took the ota's.
[X Style (Pure) Android Development] pizza_pablo:
Gotcha! Thank you, very much

Obviously, this can be flashed in TWRP....

What do you mean by, 'restore system and boot from link'?
[X Style (Pure) Android Development] ffejy462:
Not a flashible zip. Extract the backups and restore in twrp.
[X Style (Pure) Android Development] Axelsasuke:
Lock Bootloader

How to do I relock my bootloader it wont allow me with the latest and wont flash motorolas because its to old
[X Style (Pure) Android Development] pizza_pablo:
DLed, extracted, placed in the TWRP backup /nandroid folder, wiped data, system, dalvik & cache, restored your nandroid, used the REBOOT SYSTEM button, no joy. Same result.

I really appreciate your trying to help!

I emailed Moto and asked where I could find the latest firmware, because what's on their site is ancient.
[X Style (Pure) Android Development] ffejy462:
Huh. Darn. Hope you get it sorted.
[X Style (Pure) Android Development] Hemidrosis:
Flash the September firmware.

Skip flashing gpt.bin & bootloader.img. Flash everything else

Also, don't erase userdata as it will bootloop.

If successful, you can choose to take the Dec. OTA or not.
[X Style (Pure) Android Development] pizza_pablo:
Thanks!

I've read that downgrading, even security updates, leads to bootloop, or is that just OS.

Come to think of it, I reckon I don't have much to lose.

---------- Post added at 08:03 PM ---------- Previous post was at 07:12 PM ----------

None in the OP are from September.

Do you mean to use the September 2015 FW from the Motorola web site?