yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] gokart2:
Updated the OP with XT1572 "STYLE" firmware, etc....
[X Style (Pure) Android Development] gokart2:
make clean && make mrproper
[X Style (Pure) Android Development] chispas117:
I have no clue how to understand this lol, if I could I would :(
[X Style (Pure) Android Development] gokart2:
I have no clue either...lol!
[X Style (Pure) Android Development] amit.lohar:
its a silly error. that line is blank that's why that error.

delete that line and it should work..i did for you,,you can try that one.
[X Style (Pure) Android Development] amit.lohar:
[MENTION=4267845]gokart2[/MENTION] if my previous upload didn't work here is the second. You didn't close the bracket for assert at line 9
[X Style (Pure) Android Development] gokart2:
Thank you very much!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!:good::good::good::good::good:

I appreciate the help very much! I'm gonna give it a try and see.

I see that I didn't close it now. I built about 10 of these....so I probably thought I had it closed in this one like the others.

And I thought we were supposed to leave one blank line at the end?
[X Style (Pure) Android Development] gokart2:
Update...... I got the installer-script figured out. It flashed, but after sitting at the splash screen for a little bit it rebooted into recovery....?

I'm lost at this point. I'm gonna try to do a system dump from my device and build it that way (the way I'm used to) instead of they way I built it from the Firmware. The tool I used may have had something to do with it?
[X Style (Pure) Android Development] rickbosch:
exactly the same, yes.
[X Style (Pure) Android Development] revolagoy:
Thanks for the reply and confirmation. I am currently running TruePureXMM 2.3.3 with TWRP 3.0.2. Would you be able to confirm these basic steps to flash MPHS24.49-18-4 ? I am new to ADB commands and would really appreciate the help.

1. download the MPHS24.49-18-4 file below:

XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip

2. extract the zip file contents into my laptop ADB folder

3. connect my phone to laptop and boot into fastboot mode (I think I can do this part)

4. Copy each command line in the first post to my laptop ADB window and run each command one by one in ADB

This is where I am not sure what to do next. After I run all the commands where will end up?

I ideally would like to install Supersu 2.65, Xposed and Gravity box and that's it.

Any help you can provide would be greatly appreciated! Thanks again for your reply on the commands!
[X Style (Pure) Android Development] lafester:
Copy the lines into text file and save as .bat then run the batch file. Flash twrp, boot into twrp and flash su 2.62-3.
[X Style (Pure) Android Development] csrow:
Coming from rooted 18-3, I flashed 18-4 using the original fastboot commands except I skipped flashing the recovery to keep the TWRP recovery.

Also, 18-4 only had 9 system image parts so I skipped the last system image flash command.

I cleared the cache but did not erased user data to keep all my apps and settings.

After fastboot commands, I jumped into TWRP recovery and installed Supersu 2.76 systemless root before restarting the phone.

Everything is working great.
[X Style (Pure) Android Development] revolagoy:
Do you know which Supersu to install to use exposed? I have 18-4 up and running.
[X Style (Pure) Android Development] revolagoy:
I installed Supersu 2.62-3 as recommended and xposed is up and running.

Thanks for the help!
[X Style (Pure) Android Development] m3kgt99:
Guys,

I just want to start by saying that I had a Galaxy S3 before and it was SO much easier than this new XT1575. I'm trying to figure this out. I just want to get rooted so I can install Titanium and some other apps that require root access. I followed ivcarlos' thread by unlocking my bootloader, installing minimal adb, downloading the files attached at this threadand now I am at the following:

Steps:

1) extract files in a folder of your choice (su.img, boot.img). DONE

2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder. (In the ADB folder?)

3) enable USB debugging on Android. DONE

4) connect your device on pc. DONE

This is what I don't know what you're talking about

5) open a command prompt in a new folder.

6) type "adb push su.img /data/local/tmp" without quotes.

7) type "adb install Superuser.apk" without quotes.

What does he mean "open a command prompt in a new window"?

I looked through this thread and so many others and I'm not quite getting it.

The other issue is that when I load the OTA updates, it works fine except where the phone restarts and goes into TWRP and it never applies the update and eventually it will just fail. Any suggestions? Maybe I just need CM13.0 haha
[X Style (Pure) Android Development] shoman94:
So you used this commnd:

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot flash system system.img_sparsechunk.8

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 reboot

I removed the last system.img, flash recovery and erase userdata?

Thanks.
[X Style (Pure) Android Development] csrow:
Yes, those are the fastboot commands I used except don't reboot at the end.

After those commands are finished, just go to TWRP recovery and create a text file first to force systemless root. Then install the supersu zip. If you want it automated, there is a TWRP installable zip file which contains the script to create the text file first before installing supersu. (search on systemless root thread)

I haven't tried but you may also want to skip the logo flash since the default logo will warn you about the unlocked bootloader. Or you can just flash the modified logo after the system root is finished.
[X Style (Pure) Android Development] StankFiss:
Just curious why doesn't Motorola push the latest security patch out instead of us having to flash this. Is the latest legit and what do you gain from it? 6.0 MPH24.49-18-4 FIRMWARE
[X Style (Pure) Android Development] OldBaldy:
There is an OTA available for the patch, at least on Verizon. My friend just got it. I'd already loaded the -4 firmware so did not get the notice.
[X Style (Pure) Android Development] SR3TLAW:
So what and where can one find Verizon stock firmware. So many "back to stock" threads.
[X Style (Pure) Android Development] notjaykay:
I don't believe there's actual stock "Verizon" firmware for this phone.

For what it's worth, on my MXP that is on VZW, I used the latest 6.0 MPH24.49-18-3 firmware from the OP to bring my phone back to stock.
[X Style (Pure) Android Development] SR3TLAW:
Appreciate it. I will PM you also - be on the lookout
[X Style (Pure) Android Development] Tanker Bob:
Finally got the May update working

This seems to have worked perfectly for me so far. All my apps and data were preserved. The About screen verifies that all is well on the May update. Here's the commands I used in the Linux terminal after backing up the old system in TWRP:

sudo fastboot flash partition gpt.bin

sudo fastboot flash bootloader bootloader.img

sudo fastboot flash boot boot.img

sudo fastboot flash system system.img_sparsechunk.0

sudo fastboot flash system system.img_sparsechunk.1

sudo fastboot flash system system.img_sparsechunk.2

sudo fastboot flash system system.img_sparsechunk.3

sudo fastboot flash system system.img_sparsechunk.4

sudo fastboot flash system system.img_sparsechunk.5

sudo fastboot flash system system.img_sparsechunk.6

sudo fastboot flash system system.img_sparsechunk.7

sudo fastboot flash system system.img_sparsechunk.8

sudo fastboot flash modem NON-HLOS.bin

sudo fastboot erase modemst1

sudo fastboot erase modemst2

sudo fastboot flash fsg fsg.mbn

sudo fastboot flash bluetooth BTFM.bin

sudo fastboot erase cache​

I skipped the logo image so as not to get the silly bootloader unlocked warning, and skipped the recovery image to preserve TWRP 3.02-0. After flashing all this, I booted into TWRP, opened the terminal and typed "echo SYSTEMLESS=true>>/data/.supersu" without the quotes into the terminal, then flashed SuperSu 2.76 which installed systemless. After that, I rebooted and Android updated with no problems.

Thanks for ploughing the road for us!
[X Style (Pure) Android Development] devsk:
My MXP is running firmware from 2015 (1255309.10.1.68R). I am running CM13 on it. I want to go to the latest firmware but don't want to flash boot, recovery or system, and neither do I want to erase user data.

The following sequence should work, right?
[X Style (Pure) Android Development] devsk:
And I lost the radio with this approach...:( It can't find TMobile or any other network. APN is correctly selected. But I don't get anything under Network Operators. It pops toast saying "Error while searching for networks".

How could this lead to loss of radio?

---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------

What I see is that when I am in the booloader mode, I see baseband of 1255309.10.01.68R, which is still old. All the commands to flash the various pieces succeed fine, but the baseband in bootloader is still old. Does anybody know how this happened?
[X Style (Pure) Android Development] devsk:
Seems like the way to restore the radio was to install the stock boot image and boot once with it. CM13 bootlooped for >15mins. I rebooted it into recovery during its bootloop, restored my boot image and it booted right back. Now, it still shows baseband 309 in bootloader but 331 inside CM13, and it finds TMobile. We will see if random reboots go away, which is what I wanted to update the firmware for (I was using 5.1.1 firmware because I updated from 5.1.1 to CM13).

---------- Post added at 12:26 PM ---------- Previous post was at 11:49 AM ----------

hmm...I had requested the latest ROM from motorola yesterday and today I got it. And its at MPH24.49-18_18. The one I got from OP was MPH24.49-18_4. Something changed from 18_4 to 18_18 for sure. Why is Moto not putting these updates out? Or is no one around here is running the stock anymore and hence no updates?
[X Style (Pure) Android Development] tony1208:
where can i dl the stock recovery?
[X Style (Pure) Android Development] mrbracht:
Did you get your hands on the 18_18? I want it . Did they happen to send a download link for it?
[X Style (Pure) Android Development] SpasilliumNexus:
I've got 18-18 a few months ago. It's only Marshmallow without security updates, and was zipped all weird. Thread about it here (download link doesn't work anymore since I deleted the file): http://xdaforums.com/moto-x-style/general/request-marshmallow-factory-image-moto-t3324313
[X Style (Pure) Android Development] buggerritt:
That's odd. I just downloaded it from Motorola. So, that's not the one with May security update? Why is it the latest from Motorola, then? Why would 18-4 be an update but 18-18 is not? I'm so confused.
[X Style (Pure) Android Development] rsmiff:
I flashed the 6.0 MPH24.49-18-3 FIRMWARE with the 6.0_boot.img and 6.0_recovery.img from the OP but after boot I have no wifi. I can't enable it. I noticed when I flashed the modem I got an error regarding a "slot"? I can try to reproduce it to be exact. Any advice?

edit: I flashed all of the XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml files and all is well.
[X Style (Pure) Android Development] NelsonCastrone:
Hi, I got a motorola xt1575. After the May update it got stuck in a boot loop. I got the bootloader loked since I cant boot and chek "Allow OEM unlock" in Developer Options.

So I downloaded XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml

I can execute this commands with no trouble:

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

but i got problems with this:

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

It said that "preflash validation failed"

I guess when the first 4 sparsechunk were succesfully flashed they messed up my system partition, now i got a "Start up failed" message saying something about "failed to validate system image"

I've tried to downgrade or install the stock image but with no luck. I think it because i have the bootloader loked

Any help will be really apreciated
[X Style (Pure) Android Development] StankFiss:
Has nothing to do with bootloader unlocked or locked.. Your system was corrupt in some way. Flash February update. Then let it over the air update or flash update. Of course do not install TWRP or SU till its been update with May. For the May update to be flashed you have to use stock recovery. Pretty sure but don't quote me on that.

Oops. Sorry yes your bootloader needs to be unlocked.
[X Style (Pure) Android Development] CLETjB:
Couldn't I just flash XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip from TWRP 3.0.2, or would that be to simple?
[X Style (Pure) Android Development] mikeoswego:
The files in that zip are not in a TWRP compatible format. You used fastboot to unlock your bootloader and to install TWRP in the first place and that is what you use to flash this file. Doing this will take your phone to the current version of the Motorola stock software. The instructions are in the first post but I'll post something slightly different here. Save these commands as a file with a .bat extension and you can run it from the same directory where you extracted the files from the above zip file (or you can copy and past each line one at a time into the command window):

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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 reboot

In the above commands, I left out the following commands that are given in the first post. The first one (logo) will reflash the startup splash screen, if you have already replaced that with one that doesn't have the unlocked bootloader warning, there is no reason to flash this one. The second line (recovery) will install the stock recovery replacing TWRP, only do this if you don't want TWRP anymore. The third line (userdata) will erase all of your settings, your installed apps and all of your files saved in internal storage, that is effectively a factory reset and you only need to do this if there is some problem, simply upgrading to the latest version from another stock version does not require this normally. If you do want to do any of these, do it before the final 'fastboot reboot' command.

fastboot flash logo logo.bin
fastboot flash recovery recovery.img
fastboot erase userdata
[X Style (Pure) Android Development] CLETjB:
Thank you for your quick response, and explaining the steps at bit more clearly.. I also have ChainFire's FlashFire to help with backups, I create fastboot backups..
[X Style (Pure) Android Development] mbircher1029@gmail.com:
Thank You So Much!!!!!!

I have been trying to figure out how to get the stock image back, i surfed online to find the image and all I had at first was Feb security update, and i was not able to load all the files, (specifically gpt.bin and HLOS) Now it is up and running thank you so much
[X Style (Pure) Android Development] eigerzoom:
can i get a mirror for the may 1st update

i'm not a kim dotcom fanboi, and certainly not installing browser add-ons just to dl this.
[X Style (Pure) Android Development] RunnersFoot:
Just curious if it's expected behaviour that this stock rom doesn't give heads up notifications for Gmail and inbox? Coming from various custom ones they all had heads up for these apps.

So just curious if I have a problem. Or if this is normal.
[X Style (Pure) Android Development] StankFiss:
Abnormal. Mine shows email in notification and also shows a number on the app icon on how many emails are there.
[X Style (Pure) Android Development] Sporttster:
I'm wanting to update from 5.1.1 to the latest stock firmware. I am BL unlocked presently and am rooted. Now if I do this, using your stock image here with May update, I'll be able to remain unlocked BL?? I know that I'll have to do a systemless root following the update. When you say completely stock, are you meaning no root, no unlocked BL or does the BL remain unlocked when doing this? As far as I know, there's no difficulty re-rooting this with the May update, correct? Want to make absolutely sure that if I do this I don't lose the ability to have the unlocked BL AND get rooted again. One last question....on the latest with May update, hotspot is still functional, correct? Just turn it on and it works? Correct? Do not want to lose that functionality. Thanks!!!
[X Style (Pure) Android Development] StankFiss:
Your bootloader will stay unlocked. Firmware is a stock branded rom of the phone. No matter what firmware or rom you put on your phone the bootloader will stay unlocked. But as far as root you will lose root each time you change the firmware or rom. Bootloader and firmware/rom are two different entities. Yes you can root May update with no issue using systemless method. Yes functionality of the phone is the same.

Keep in mind I have a xt1575. I reinstalled the Febuary update firmware. Then let the phone manually updated the phone over air with no issues. Some people flashed the May update with BT and Wifi issues but can be fixed by flashing the BT.bin separately. In other words read read read read. And before you step any further read read read some more.
[X Style (Pure) Android Development] Sporttster:
Yeah I 'read' about the BT/WiFi issue. Guessing that's just a luck of the draw thing? And it's ok to take any OTA updates and still root? Because I may just do that, let it get all the OTA's out of the way and then root it, if that works ok.
[X Style (Pure) Android Development] omaralkha99:
noob question, but if I were to flash the latest firmware then my custom rom on top will this still work?

the reason I am doing this is because im having major battery loss due towards cell standby
[X Style (Pure) Android Development] SR3TLAW:
Stupid question. Read read read
[X Style (Pure) Android Development] Sporttster:
I DL'd the MPH24.49-18-4 FIRMWARE with the May security update. I have the TWRP app on the phone and to proceed, I flash this with that app doing a BU/Wipe data/cache/Dalvik wipe, correct? And as long as there are no issues I'm GTG. ? Making sure I dot my i's and cross my t's here, so bear with me. Don't need a bootloop..
[X Style (Pure) Android Development] xpakage:
And an even "more stupid" answer.

What is "will this still work"?
[X Style (Pure) Android Development] SR3TLAW:
Wanted to apologize man. Saying this was not proper forum etiquette. It was late and I was pissed about some Jr Level Tech breaking **** at work. This shouldn't be a place for any hostility.

Good luck
[X Style (Pure) Android Development] StankFiss:
Why bother with the firmware. Just flash the custom rom you want. You do not need moto's firmware.
[X Style (Pure) Android Development] Sporttster:
I want to get this done this weekend. Is this ok to do? Don't know whether to use Fastboot or TWRP to flash this or whether both are equally ok to use.
[X Style (Pure) Android Development] tonyc0642:
The OP needs to be updated to include the September 1st firmware on Moto's website. It would be a lot easier than going through the OTA process just to get back to updated stock.
[X Style (Pure) Android Development] jdgesmlls:
The Sept. 1st firmware has the same version as this link from the OP under Android 6.0:

"Motorola Supplied Firmware

Moto X Pure Edition (2015)

MPH24.49-18_18"

Although the Moto site says this is "6.0.1", as far as I know it is 6.0 with May security patch. Why update it if it is already there?
[X Style (Pure) Android Development] tonyc0642:
Because I didn't know there was a difference. Update it, don't update it, whatever. Just trying to contribute.
[X Style (Pure) Android Development] jdgesmlls:
This thread confirms the Sept. 1st "update" is actually 6.0 with Nov. 2015 security patch, as in the first 6.0 release: http://xdaforums.com/moto-x-style/general/xt1575-android-6-0-1-factory-image-t3458286

'Motonovo' strikes again... and they are distributing firmware not only labeled the wrong Android version but with a 10 month old security patch. :silly:
[X Style (Pure) Android Development] dmb219:
I'm a big fan of being up to date with the latest of everything & will probably grab the Pixel XL or whatever it's called, but this phone has been everything I could ask for. The current stock firmware is rock solid for me. The camera is fair/good, speakers are awesome. If/when I get a new phone I will unpack it carefully in case it gets returned because it can't keep up with the Moto.
[X Style (Pure) Android Development] atmadhibrata:
thanx.

you help me so much.

keep your excelent job:laugh::laugh::laugh::laugh:
[X Style (Pure) Android Development] 4rm:
Edit: Sorry, fixed my issue, was flashing the wrong image.
[X Style (Pure) Android Development] PINOM:
idk if anyone figured it out but i think it should be...

fastboot flash bootloader "x".img

instructions would just be missing last part
[X Style (Pure) Android Development] Mohannad-K:
Any one have stock kernel IMG file for 6.0.1?

Or at least new version of 6.0 as the IMG file in first post is 2015 old version
[X Style (Pure) Android Development] jdgesmlls:
Software status

Does anyone know if there is a way to get "Software status" back to "Official"?

I fastboot installed MPH24.49-18-4 and it still shows "Software status: Modified". I still have the bootloader unlocked of course so I don't know if that has something to do with it either...
[X Style (Pure) Android Development] lafester:
Unlocked=modified
[X Style (Pure) Android Development] Prazaar:
My Software Status with TWRP and CM13 is still offiziell. Will never change after flashing.

I have no idea why...
[X Style (Pure) Android Development] jason2678:
Ignore
[X Style (Pure) Android Development] ezeuba:
How to extract and flash MPH24.49-18_18

If anyone can guide me on how to extract and flash the MPH24.49-18_18 firmware I would be happy. I downloaded it as a gz file and when I extract it shows a file without an extension. Infact it says it is a 49-18_18 file. I cannot see the different components of the firmware to flash with fastboot. Please help. Thanks.

NB Never mind. I figured it out. I had to append .gz to the file and extract again.
[X Style (Pure) Android Development] SR3TLAW:
Is what you posted the magic combo for a fully functional Verizon installation? Im coming from TruPure so the modem/bluetooth work fine. Im keeping TWRP so I skip the "fastboot flash recovery" but what about the commands below. Should I retain them from TruPure?

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot flash bluetooth BTFM.bin