yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] robn30:
Tried it, and no joy. This is a bit frustrating. How long is it going to take to get this stupid update to register and show up. Sucks sitting here with no TWRP or root waiting for this update to show so I can take it then get back to business. Might have to consider the Moto Z just so I can get 6.0.1 and a AMOLED display. Worst part is I haven't even had this phone a year yet. I am very disappointed with Motorola's update schedule, especially since they purport Pure Android. It's not like they are doing some extra development because they are carrier locked and branded, like Samsung's devices. I am officially annoyed.
[X Style (Pure) General] robn30:
So I restored my rooted backup using TWRP, I couldn't wait any longer, and when I defrosted the Moto Update app, it immediately found the February OTA and downloaded it. I moved it from cache to my Ext-SD and attempted another Software Update search and it came up with the February Update again. So I guess my device just hasn't received the May Update yet. Is it possible I have to install the February Update first before the May one will be detected?
[X Style (Pure) General] acejavelin:
Yes, the updates are incremental... You must apply the February update first, then it will see the May update.
[X Style (Pure) General] robn30:
Okay so I flashed back to my clean stock unrooted software from earlier and reflashed the stock recovery image. I then moved the downloaded update zip file to the root of my SD and tried to install it using stock recovery. It gave me an Error Status 7 saying "/system/app/3c_main/oat/arm64/3c_main.odex" has unexpected contents"

What the heck does that mean? Why is this so darn difficult?
[X Style (Pure) General] acejavelin:
Something in /system has been modified and not restored to stock... it is telling you what file. Your system must be PURE stock,not just unrooted and flash stock recovery.
[X Style (Pure) General] robn30:
Well I just flashed back the OEM software from Moto once again and tried to install the update zip file from my SD using stock recovery, and once again I am getting the same error. It doesn't get any cleaner than the software from Motorola. I am at a loss and now I will just pray that we get an update to Android N at some point. I'm not willing to wait using stock software for the update to register to my device again. Unless some one can enlighten me to what I might be doing wrong, I'll just flash back to my TWRP rooted backup.
[X Style (Pure) General] acejavelin:
I got nothing, sorry... If you installed the OS clean, booted it up and went through the setup, and tried to apply the update via the stock location in cache it should work. I don't know what else to say.
[X Style (Pure) General] robn30:
That's part of the issue, if I boot and setup, I can't get it to register the update. It just keeps saying my system is up to date. I am on my last go round. I have just reflashed clean again and did a full factory reset so there is absolutely no sign of anything other than a perfectly clean system. Is it possible that the file referenced in the error isn't supposed to be there? Wouldn't flashing the system image that I downloaded from Motorola remove it if it isn't supposed to be there?
[X Style (Pure) General] acejavelin:
Yes, but there is probably a configuration piece missing that is caused by the setup wizard... I don't know.
[X Style (Pure) General] HikingMoose:
Omg people. It's not the carrier. I can't say it enough. My wife has the same carrier, so do my co-workers. They'll be sitting right next to me with no issues. How is that carrier related???

Sorry to be short, it's just that you're the 4 person saying it's not the phone is the carrier. It's not possible that is the Carey carrier. USCellular blows away all other carriers in Maine.
[X Style (Pure) General] Silarn:
What I'm saying is it's definitely possible the phone has issues on your network - or even any LTE CDMA network (which US Cellular uses). I personally have not had switching problems on AT&T's network, which uses totally different network types and radios.

Meaning the carrier might contribute in terms of what data types it's using and what your phone has to switch between or even the coverage in your area. This is not identical between all carriers. But in your case it does sound like the phone is at fault in some way.
[X Style (Pure) General] GnusNat:
This, I'm rooted on February update with customer recovery and until someone figures out a way to apply this update can we at least stop the damn thing

from popping up every 5 mins??
[X Style (Pure) General] ahent:
I was unable to get update no matter how many times I told phone to look for it. I pulled my Verizon Sim and phone all of a sudden said there was an update. Weird. Completed update, pooped Sim back in and all is good.
[X Style (Pure) General] evandena:
I've found you can at least select remind me later, and set the time for 23 or whatever hours later. Then it's only a once a day pop-up.
[X Style (Pure) General] robn30:
Have you unlocked and rooted your device or is it completely stock? I received the update and pulled it from cache. I completely restored my device using the Motorola supplied software but when I try to apply the update from sdcard using stock recovery, it errors out. Also gets the same error when trying to apply the update via adb sideload. I can't get it to take no matter what I do.
[X Style (Pure) General] ahent:
Stock unrooted. I only rooted for unloading bloat and a few visual tweaks. With this phone there is no bloat and I can live without tweaks.
[X Style (Pure) General] HikingMoose:
Ok I see. I'm not sure of the cause, I just know it's very annoying and making me want to get rid of my first ever Motorola. One of the other people that responded to my hand-off issues agreed that he has the same issue, and forces his to stay in 3G to prevent the slow hand-offs. In other thread there are several people complaining of the same issue.

I doubt they have my carrier, but maybe. I'll stick this phone out a little longer until something really tempting is released, then I'm dumping Motorola lol. I am really surprised that Moto updates their phone's slower than Sammy (and everyone used to say Sammy was the slowest ever). I see no perks to Moto. No updates, poor reception (when compared to LG's and Samsung's right next to me), frequency band hand-offs, and the choppy scrolling (which I've been able to improve).
[X Style (Pure) General] robn30:
For the love of God, I finally got this thing updated to the May update. It was almost a mission that I had to conquer, I just couldn't give up until I found a way to get it done. In the end I had to flash back to Lollipop using Shawn5162 restore to stock tool. I also had pulled my SIM for this entire process, as I heard that was a good way to ensure the update would be detected quickly. I can say that the SIM trick is a fact. After flashing back to 5.1.1 as soon as it booted and I selected Software Update, it immediately found the MM update. I installed it and it then immediately found the February Update, then the same thing with the May update after the February update was installed. I then performed root using SuperSU Beta 2.74-2 after I flashed TWRP 3.0.2-0. Made sure to use TWRP terminal to enter echo "SYTEMLESS=true" >> /data/.supersu. I am restoring my apps via TiBu as I write this. My MXPE is now fully up to date. I will now eagerly await Android N.

By the way I did make TWRP backup of my unrooted May Update before rooting. Hopefully that will save me when Android N comes along.
[X Style (Pure) General] GrandAdmiral:
Does anyone know what folder the update is located?
[X Style (Pure) General] bertlanerd:
Same here. Was looking for an ADB version to side load and found this thread. Unrooted, just unlocked and flashed back to stock recovery. Blarg! Flash TWRP, wipe cache, ignore update, wait for N...
[X Style (Pure) General] lottanookie:
note: My Moto is not rooted but I *do* have the bootloader unlocked.

I got the notice to download, then did the download, then said YES to update, then it rebooted after installing, then went into the TWRP loop. So I wiped the cache, then rebooted. The phone boots up but is back to showing the version as 6.0 February 2016 Update and not the one I had just downloaded.

Tried it again this time taking out the SD card. Same thing happened.

I'm out of things to try at this point.
[X Style (Pure) General] SpasilliumNexus:
/data/data/com.motorola.ccc.ota somewhere in there. cache probably. it's been a while since I pulled one.
[X Style (Pure) General] SR3TLAW:
Do you know where to get Stock ROM for us Verizon users by any chance?
[X Style (Pure) General] G41LAH:
Has anyone checked the recovery log? I'm getting a MPHS24.49-18/18 error. Says it expected MPHS24.49-18/03 or 04/05. By the way the top of my recovery says MPHS24.49-18/18 can the ota be edited to accept this? Can't find the zip anywhere.
[X Style (Pure) General] ahent:
SR3TLAW, this phone is not carrier specific, so the stock rom will work with all US carriers. All you need is a Verizon Sim to work with Verizon.
[X Style (Pure) General] G41LAH:
Fixed update error!

For those of you who are having an issue flashing back to stock, and trying to apply this update, here is how I fixed it, go get the previous update (February) ota zip, apply it, then try the July (May) update, and it should work.

I know it seems strange to apply the February update on top of itself, but it works! Seems to patch and fix whatever is preventing the latest security update.
[X Style (Pure) General] SR3TLAW:
Think that's part of the problem. So many choices. Can you point me to a flashable zip
[X Style (Pure) General] ahent:
I believe this links to stock rom with February update. I haven't changed my rom at all on this phone so as far as instructions or effectiveness of this link I can't say. http://xdaforums.com/showthread.php?t=3323126 crap this link points to end of thread just go to the beginning and there u are.
[X Style (Pure) General] SR3TLAW:
Thank-you [MENTION=4570974]ahent[/MENTION]

What ROM are you running?
[X Style (Pure) General] ahent:
Just plain old stock, not even rooted. I used to root to kill bloat but this doesn't have any.
[X Style (Pure) General] aybarrap1:
Same here. I pay for apps I like in order to remove ads and don't use those that don't provide the option so ad blocking is not an issue much. About the only thing I miss is some profiles i created in the app Tasker since it automated so many things for me. I can live without them though since I prefer to keep my warranty on an already smooth running phone. Will probably root after my warranty is up just to get those profiles back and ad blocking for web pages.
[X Style (Pure) General] lottanookie:
My phone has just an unlocked bootloader. It's

not

rooted. Upon installing the new OTA update, my phone then reboots and goes into a Team Win loop where the TeamWin logo flashes over and over.

I then forced it to reboot into TWRP, I clear the cache, and try to boot up again, phone still goes into the Team Win Logo screen loop.

Then I restored my Moto from the backup I made from the Feb update and all is well.

And then, once again, the OTA update signals it's ready for download/install.

SIGH....

I need a zip file that I can load directly from TWRP that will work, because my Moto X Pure 1575 will not update to this newest security update from the OTA file.
[X Style (Pure) General] G41LAH:
You need to be on stock recovery as well. Here is a flashable zip I found, forgive me if it was from a post here on xda, as I couldn't remember exactly where I found it.

https://drive.google.com/file/d/0B5AiGacWcBRzTFZHYTRrQk42UGM/view

Then re flash the February OTA zip, and you should be able to take the latest update. You will need to re flash TWRP, I would suggest the latest build from source posted here:

http://xdaforums.com/showpost.php?p=67332448&postcount=1
[X Style (Pure) General] acejavelin:
You need to restore stock recovery, TWRP is the problem not root or no root.
[X Style (Pure) General] lottanookie:
Well now I may have screwed myself...

I mistakenly 'wiped' the entire system

doing a 'wipe' from TWRP, including the OS (dumb I know). Like nothing left, no backups, nada.

So I used this tool: Moto X Style/Pure Edition "Restore-To-Stock-Tool

and that worked to restore me back to 5.1.1, but the screen warning the bootloader is unlocked still appears.

AND, more importantly

NO WI-FI capability. I cannot turn on my Wi-Fi radio at all.

Can't download an OTA update.

Plugging my Moto into my computer -- computer does not recognize the Moto. Yes I re-enabled Developer Options to allow USB Debugging.

So I'm only 'sort of' restored because without working wi-fi I can't really go to the next steps.

NOW WHAT?
[X Style (Pure) General] acejavelin:
One-click tools are bad news... Look in the Developer sections and you will find do the stock images, flash them manually with fastboot, paying special attention to the radio section (sometimes you have to do them 2 or 3 times). You are not screwed, calm down and have patience.
[X Style (Pure) General] aybarrap1:
If that is not working, you can try to do the software image directly from Motorola and see if that works. Your bootloader will remain unlocked and therefore flagged.
[X Style (Pure) General] SR3TLAW:
I feel that. The stock experience is why I bought the phone. I do love Xposed though. Does odexed ROM still break VoLTE on Verizon?
[X Style (Pure) General] lottanookie:
It took hours but I've gotten my phone UNbootloaded, I got it back to stock, found a link outside of xda where the radio file was available for download and flashing. Once all of that was achieved then I started downloading OTA updates, sequentially, installed each, downloaded the next OTA update, lather, rinse, repeat until I finally FINALLY am on the current OTA release.

Because the 'Bootloader Warning' screen continues to appear, I found the replacement image and flashed that to the phone (note: every time you update firmware you will have to re-flash the replacement image or you will once again get the 'bootloader unlocked' screen).

Then came the ultra-tedious task of downloading apps, installing, configuring each screen the way I wanted (I had taken screen shots).

UGH

So I am Not rooted and I have a Locked bootloader and I am not going to change any of that because trying to update firmware/OTA is a pain in the ass and also sometimes provided firmware for flashing can be missing vital things (like working wifi as one example).

I spent probably 8 - 10 hours trying to get this phone updated and then fixed and relocked and yada yada.
[X Style (Pure) General] StankFiss:
I would install TWRP without SuperSU. Make a back up with the clean install. Then mess around with phone. SuperSu is what makes it fail on OTAs
[X Style (Pure) General] aybarrap1:
I second this as far as the backup. After the TWRP backup, if you have the space on the SD card, once you root, use TiBu to do a batch backup of your apps and update it when the next OTA is available. Then you can use the TWRP backup to get a system that is not modified restored, stock recovery, etc. Do the update and reinstall TWRP and backup updated non rooted ROM. From previous experiences, I found that a factory reset for major updates helps prevent potential issues, and using TiBu for a batch restore of apps makes things faster.
[X Style (Pure) General] acejavelin:
TWRP will make OTA's fail just as quickly as SuperSU... But a backup is an excellent idea, you can boot TWRP and make a backup without installing it though. TWRP doesn't have to be flashed to the phone to do it's thing.
[X Style (Pure) General] aybarrap1:
Yes it will. But installing the stock recovery before the OTA should allow for no issues provided the system has not been modified. Hence the immediate backup of ROM upon installing TWRP.
[X Style (Pure) General] smvb64:
Hey, I'm new to the Moto X pure and just recently rooted it and installed a custom recovery. From what I can tell from this thread is that OTA updates are absolutely a pain to install haha.

Is it possible to just flash the stock recovery back to install the OTA (if so, were can I find just the stock recovery?)or do you have to flash a stock rom? The only thing that was changed was just the recovery and supersu was installed.

Thanks SM
[X Style (Pure) General] lmulli:
Flashing back to the stock recovery *may* work, as long as you haven't altered the /system /vendor partitions. Unfortunately, the stock rom images that come with this device don't have the usual .img files where you can simply use fastboot to flash the relevant partitions back to their defaults., however, it does come with an .img file for the stock recovery, so flashing back to that shouldn't be an issue.

If you haven;t touched /system /vendor then I would suggest using Flashfire to install any OTA as this will not only temporarily install the stock recovery in order for it to work, but it will also inject SuperSU into the kernel.
[X Style (Pure) General] GrandAdmiral:
Is there a simple way to verify if the partition has been modified? And if it has been modified, is there a simple way to put it back? Is it as simple as uninstalling the app?

This damn pop-up notification is annoying the hell out of me. :crying: :eek: :(
[X Style (Pure) General] lmulli:
Try updating to the OTA and if it fails, chances are something has been modified. If you use the Chainfire app, it will actually tell you that they have been modified.
[X Style (Pure) General] quakeaz:
Moto Z is getting the July patch...

https://9to5google.com/2016/08/30/moto-z-droid-security-patch/
[X Style (Pure) General] GrandAdmiral:
Is that FlashFire?
[X Style (Pure) General] lmulli:
Yup.
[X Style (Pure) General] Myvoice2:
I've never used FlashFire before but I'm really getting sick of the OTA update warning. Can FlashFire safely be used with systemless root? What are the right options to use on it since if I open up FlashFire it's not autodetecting the OTA for me. I see it in /cache but I want to make sure I have the right settings since I rather not have to wipe the phone again.
[X Style (Pure) General] GrandAdmiral:
So I tried using FlashFire last night to update. Everything seems to run well that I saw, but now I'm stuck on the Moto "M" screen. Any idea what could cause that?
[X Style (Pure) General] gskelter:
What up guys. I just received an OTA software update version: 24.221.5.en.01.

I have a xt1572 buy it in the moto maker page. Anyone have the update?

Enviado desde mi XT1572 mediante Tapatalk
[X Style (Pure) General] cookiehead2:
What's the security patch level?
[X Style (Pure) General] quakeaz:
Screenshot of device info?
[X Style (Pure) General] Antiapplekid:
Stupid question guys I have rooted my device and so forth and can't take a OTA update has there been a image that I can flash with the latest update I am getting sick of that popup lol
[X Style (Pure) General] gskelter:
Enviado desde mi XT1572 mediante Tapatalk
[X Style (Pure) General] SpasilliumNexus:
Screenshot with the patch applied...
[X Style (Pure) General] lmulli:
6.0 and February update? Bit behind the times with that one!
[X Style (Pure) General] gskelter:
Oh I see. Sorry I cannot apply the patch since my phone is rooted. For what I know I need to wait until I find a flashable zip.

Enviado desde mi XT1572 mediante Tapatalk
[X Style (Pure) General] acejavelin:
Accept it, the phone will reboot into TWRP, enable MPT mode in TWRP, find the update ota zip and copy it to PC, wipe cache and reboot. Then you can share the file.
[X Style (Pure) General] gskelter:
Thanks and will do it. Do you know where the ota get saved?

Enviado desde mi XT1572 mediante Tapatalk
[X Style (Pure) General] acejavelin:
Cache... Not sure the naming convention though, really what is needed is the URL to the file. http://www.androidsage.com/2016/01/21/how-to-capture-ota-update-url-for-your-android-device/
[X Style (Pure) General] SR3TLAW:
Most of us don't speak Spanish bud. But it looks like February 1st
[X Style (Pure) General] SpasilliumNexus:
When you get the update notification, tap download. Next, it will ask if you want to install it now. Tap no/cancel.

Then, using a root file manager, is when you'll be able to pull it.

The OTA file is somewhere located in /data/data/com.motorola.ccc.ota.

Look in app_download or cache in that folder. It's definitely in the com.motorola.ccc.ota folder somewhere, although I can't remember exactly since it's been a while since I've pulled an OTA from this phone.
[X Style (Pure) General] gskelter:
I zipped the whole motorola.ccc.ota folder but is very light and already download the update and click in install later so the update is suppose to be in the folder.

I attached the file
[X Style (Pure) General] quakeaz:
9.5Kb, that can't be. I thought it was in /cache someplace?
[X Style (Pure) General] acejavelin:
Hmmm... in combing through the ota_prefs.xml file, it references the following:

https://motorola-global-es-latam.custhelp.com/app/answers/prod_answer_detail/a_id/110711 (1MAY2016 security update)

But also an update to Blur_Version.24.221.5.clark_retla.retla.en.01 and the size is 9653591, install time is 10 minutes. Only "highlight of update" is Android Security Update
[X Style (Pure) General] gskelter:
Ok now I got it. It was under cache folder, but idk why the name is 24.201.4 and not 24.201.5 as how it shows in the software window (see attached).
[X Style (Pure) General] acejavelin:
OTA updates are weird, naming convention often is the currently installed version, not the final version. Basically they are saying you must have this version to apply it.
[X Style (Pure) General] evandena:
Hmm, looks like I accidentally hosed my phone a little bit.

I accidentally took the OTA update, which prepares to install and drops me to TWRP, where nothing happens (as expected). I can reboot out of TWRP, but the OTA tries to install again and reboots.

Anyone know what I can do within TWRP to stop the OTA from trying to install? I tried deleting/renaming the OTA cache folder using TWRP, but that seems to error out for some reason.
[X Style (Pure) General] waywardfrantz:
I just had this happen too. Luckily I had just gone back to stock so I just wiped and reinstalled. You have a little Time to poke around in settings but I couldn't find a way to disable the update.

I think flashing stock recovery would work best, if you go to a revert to stock thread one of the lines has you reflash the stock recovery. That's what I'm going to do next. Came here trying to find a way around that.
[X Style (Pure) General] Antiapplekid:
Okay guys I have my pure that has TWRP on it and it keeps prompting me to update is there a image for the new upgrade
[X Style (Pure) General] quakeaz:
What's the build number of the update you are being prompted for?
[X Style (Pure) General] acejavelin:
Haven't seen an update in months, so the last image is from August (May Security update), what build are you prompted to take?
[X Style (Pure) General] Antiapplekid:
Well I messed up my phone because I tried installing the rom with the latest security patches but then my radio didn't work so I went back to the one I had saved on my computer I am way outdated (Nov Security Update) I am just looking for the latest rom for the US based Moto X I am on Verizon I just am getting confused about all the different options. I don't have as much time as I use too to work on my phone so I have been ignoring it but I am getting sick of it
[X Style (Pure) General] quakeaz:
http://xdaforums.com/showpost.php?p=69103575&postcount=243
[X Style (Pure) General] Antiapplekid:
Thank you so much I appreciate it now I just have to figure out when I have time to install it lol
[X Style (Pure) General] acejavelin:
Seen a rumor that the Sept security update is starting to roll out in the UK... Anybody seen anything, nothing here in USA for me.

- Source - Towards the bottom