yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
I still have the xt1096 but am using an xt1575 now as my daily driver. I doubt that Moto will ever come up with a Marshmallow rom for the xt1096 and it wouldn't surprise me if there aren't any more security updates for it either (barring some major exploit that is discovered.) I don't find that overly concerning since most of these security patches are taking care of extremely obscure things that the average person just isn't going to encounter.

Having said that, if there is a security or other update from Moto, I probably will patch it into this rom since it really isn't a big effort for me to do that and it would keep my backup phone current.
[X 2014 Android Development] drewski_1:
I'm running the xt1095 MM port with xt1096 build prop adjustments and it works great
[X 2014 Android Development] rotorbudd:
Thanks,

I may have to give that a try.
[X 2014 Android Development] enchilader:
Any word on whether or not we are good to take the OTA update that has been bothering me since yesterday?
[X 2014 Android Development] Skyroket:
I'm having so much trouble blocking this latest OTA, but I can't find a suitable recovery image that will process the update. I found one for a 5.0 (we should all be on 5.1 if you're still stock) but the OTA fails to install in recovery.

Stock rooted + TWRP = No OTA install
[X 2014 Android Development] mikeoswego:
23.32-25-5-5 August/November security update

I found some time to put together some files for the security update that is being pushed to the xt1096:

XT1096-23.32-25-5-5-Firmware.zip - TWRP flashable zip to update phone firmware

xt1096-5.1-23.32-25-5-5-Mod.zip - TWRP flashable zip modified similar to previous versions in this thread

xt1096-5.1-23.32-25-5-5-Stock.zip - TWRP flashable zip to restore phone to stock

Even though this has just come out, the patch only brings it up to the August security patch level, see the attached screen shot.

If you want to restore your phone to stock with the latest software:

Flash XT1096-23.32-25-5-5-Firmware.zip

Flash xt1096-5.1-23.32-25-5-5-Stock.zip

Wipe Data & Cache

Reboot

If you want to update your phone that is currently running the ROM in this thread:

Flash XT1096-23.32-25-5-5-Firmware.zip

Flash xt1096-5.1-23.32-25-5-5-Mod.zip

If you used one of the debloat zips from the first post, flash that now

Presuming you still want root, flash SuperSU from this thread: SuperSU Release (As of the time of this posting the direct link to the download is here: SuperSU-v2.78-201609011115.zip)

Presuming you still want Xposed, flash xposed from this thread: Xposed thread you want the version for SDK22 for ARM. (As of the time of this posting, the direct link to the download is here: xposed-v87-sdk22-arm.zip)

The addon.d scripts will save & restore your current GApps setup, there is no reason to reflash the GApps

Wipe dalvik and cache

Reboot

If using Xposed, you also need the Xposed Installer app, this enables Xposed and gives you the app to install and enable modules, etc. The installer app is listed in the first post of the Xposed thread mentioned above. I would select the 3.1.1 version and the direct download link at this time is here: http://xdaforums.com/attachment.php?attachmentid=3921508&d=1477916609 Download this to your phone, find it with your file explorer, tap on it and you should be prompted to install the app.

If you want to do a clean install of this update follow the instructions above and in the first post but wipe Data in addition to dalvik and cache before rebooting. You would need to flash some GApps in this case, if using OpenGApps, micro is the smallest package that works since this ROM requires the GoogleNow Launcher (unless you take other steps to work around that.)
[X 2014 Android Development] enchilader:
Hey Mike, ran through these steps and everything seems to have worked fine except the Xposed installation. I'm not seeing the xposed app icon, and have tried installing it from recovery several times now. Any idea what's up?
[X 2014 Android Development] mikeoswego:
I forgot to mention that in addition to installing the xposed framework zip from TWRP, you also need to install the Xposed Installer app. The app is attached to the first post in the official Xposed thread which is here: http://xdaforums.com/showthread.php?t=3034811 I would select the 3.1.1 version, the direct download link at this time is: http://xdaforums.com/attachment.php?attachmentid=3921508&d=1477916609

Download the app to your phone, find it in your file explorer, tap on it and you should be prompted to install the app. This will enable Xposed and give you the icon to manage your Xposed modules. I've update the previous post with this info.
[X 2014 Android Development] enchilader:
Hmm alright, I'll try this out this weekend. I tried to do a fresh install yesterday but couldn't get past the activation screens, looks like google play services were messed up no matter if I installed the micro, nano, or mini gapps package. Going to try to revert to stock this morning, but as of right now my phone seems to be kinda soft bricked.
[X 2014 Android Development] mikeoswego:
This may be a Webview problem. It's been a long time since I've clean flashed anything and usually I go with the Super or Stock package with some things not installed using a .gapps-config file. I see in the OpenGapps thread that there is some ongoing issue with Webview. Setup can't complete without the rom either having Webview (which is included in the rom) or Chrome installed. There were recent versions of OpenGapps that didn't correctly install Chrome in place of Webview and then also deleted Webview causing the problem you have described (can't get past activation screens.)

If you have a TWRP backup, I'd restore it and then just dirty flash the rom update. If not, there are instructions in the OpenGapps thread for modifying the OpenGapps zip to fix the problem of Webview being deleted with no Chrome being installed. Or go with the Stock OpenGapps which does install (not remove) webview and use the gapps-config file to control what apps are actually installed.
[X 2014 Android Development] enchilader:
Interesting, this does sound like my problem though. I was hoping to be able to configure what apps were installed by the Gapps package, so looks like this should directly address that. I'll take a peek this weekend. Meanwhile, I'm back on stock with an at least functional phone. Thanks for the help.
[X 2014 Android Development] bcmyspace:
Hey Mike

Thanks for all the updates. I just updated to the new security update and like always it works perfectly fine. I had one hiccup, I can't seems to encrypt my phone anymore. Would this happen to be because of a bad configuration on my end or do I just lose the ability to encrypt my device?

Once again thanks for the updates Mike.
[X 2014 Android Development] mikeoswego:
I'm not real familiar with using encryption but I found that the phone would not encrypt when I had SuperSU installed. I had to install the stock rom, then I was able to get the phone to encrypt and it stayed encrypted when I then flashed the modified rom with OpenGApps, SuperSU, etc.
[X 2014 Android Development] D.A.N.:
Order of installing new zips files after already installed stock based rom

What order do I install these three files once i have installed the stock based rom?

Thanks you

---------- Post added at 05:15 PM ---------- Previous post was at 04:49 PM ----------

Hello, I have the phone rooted and this rom installed. Will the phone run fine without installing this update?

Thank you
[X 2014 Android Development] drewski_1:
It will run fine . . . just less secure . . . but there's been a lot of other security patches Moto hasn't merged so . . .
[X 2014 Android Development] mikeoswego:
You can install those files in any order but do them all during one TWRP session. In other words, don't try to flash one or two of them and then try to reboot the phone without flashing the last one.

Like Drewski said, the phone will work fine without applying those updates. The phone will technically be less secure without those patches but what they patched was pretty obscure anyway and there are now lots of unpatched things on this model phone since it is basically unsupported by Moto now. I wouldn't be afraid to run the phone without this patch.
[X 2014 Android Development] D.A.N.:
So what order do i install the new updates along with everything else to ensure a proper install? Some of the first list are not in the install order mentioned in first paragraph.

In addition to TWRP mentioned next, you'll need a few files on hand to complete the process:

XT1096-23.32-25-5-5-Firmware.zip - TWRP zip to update firmware.

xt1096-5.1-23.32-25-5-5-Mod.zip- The factory based modified ROM

A GApps package, this is possibly the most confusing part for new ROM flashers and will be discussed below.

xt1096-5.1-debloat.zip - Optional, removes some Verizon bloat, see list below

xt1096-5.1-debloat-keepconnect.zip - Same as above but retains Moto Connect and some files need for the Moto Gallery app.

If you want root, flash SuperSU from this thread: SuperSU Release (As of the time of this posting the direct link to the download is here: SuperSU-v2.78-201609011115.zip

If you want Xposed, flash xposed from this thread: Xposed thread you want the version for SDK22 for ARM. (As of the time of this posting, the direct link to the download is here: xposed-v87-sdk22-arm.zip

vs

Return to the Home menu in TWRP, select install, then add zip. Select xt1096-23.32-25-5-2_gpt.zip. Tap add zip again and select xt1096-23.32-25-5-2_Firmware.zip. Tap add zip again and select xt1096-5.1-23.32-25-5-2_1.zip. These 3 must be first. Tap add zip again and select the GApps zip file that you selected. If you are debloating, tap add zip again and select that zip file. If you want the CM AudioFX, tap add zip again and select that zip (you can actually do this step in the future by itself if you want.) At this point you have at least 4 zips and possibly 6 selected; slide the slider to begin the flashing process. This will take a while, don't interrupt it. If the screen turns off, use the power button to turn it back on. When done, use the Reboot System button to restart the phone. The phone will reboot, it will show the logo and then the boot animation. It will take 4-5 minutes during which time the boot animation will appear to be stuck, don't panic, this is normal and will only happen the first time after a clean install. The phone should start an optimizing apps process and when that completes, you will see the first set up screen.
[X 2014 Android Development] mikeoswego:
Ok, the second quote above is talking about the 23.32.25-5-2 version of the files, the first quoted paragraph above is talking about the 23.32-25-5-5 version of the files (which are the latest that I created.) If you installed this rom using the instructions in the first post, you are probably already running the latest version in this thread. Look at the screen shot in this post: Post 1108 and compare the build number there to what is on your phone now. If you have the build ending in -2, you can follow the instructions in that post to upgrade to the build ending in -5. Like was mentioned before, that latest build only fixes rare security issues as of August 2016; it may not be worth your time if everything is working ok for you now.
[X 2014 Android Development] D.A.N.:
My phone just ask me to update with a Verizon security update. Will this brick the phone?
[X 2014 Android Development] D.A.N.:
Just received bug report from Verizon update

I have had no problems with this rom until my phone just asked me to update with a Verizon security update. Will this update brick the phone?
[X 2014 Android Development] D.A.N.:
No matter what I do, my phone always boots up and says "unfortunately, google play services has stopped" and I can't go any further. I wipe system, data and cache. Then I install •XT1096-23.32-25-5-5-Firmware.zip - TWRP zip to update firmware.

•xt1096-5.1-23.32-25-5-5-Mod.zip- The factory based modified ROM

•A GApps package, this is possibly the most confusing part for new ROM flashers and will be discussed below.

•xt1096-5.1-debloat.zip - Optional, removes some Verizon bloat, see list below

•	xt1096-5.1-debloat-keepconnect.zip - Same as above but retains Moto Connect and some files need for the Moto Gallery app.

Then I reboot.

Any help would be appreciated.

Thanks
[X 2014 Android Development] mikeoswego:
For a test, wipe system, data, cache and then flash just the firmware and stock zip files and see if the phone will startup normally. Presuming it does, go back into TWRP and wipe system & data, flash the Mod zip file and then the GApps package (make sure you select the right package, it must be ARM (not ARM64) and Android 5.1 to work with this rom. On the debloat zip, only flash one or the other (I recommend the one that has keepconnect in the name) (Once the firmware file has been flashed, you don't need to do that one again, though it won't hurt if you do.)
[X 2014 Android Development] D.A.N.:
Google Play services still stopping

Thank you for your response. The first part wored perfectly and went back to stock. Then when I try the second part the issue comes in again when the phone restarts. I verified the gapps also. Any ideas?
[X 2014 Android Development] mikeoswego:
Ok, the GApps package will replace play services that is in the ROM. I have to presume something is going on with the GApps package. Which GApps package are you using? From the first post: Note: Due to changes in the Open GApps package, the minimum level that will work correctly with this ROM is the Micro package, the nano and pico packages probably won't work.
[X 2014 Android Development] D.A.N.:
I have attached a screenshot of my files. The gapps is new.
[X 2014 Android Development] mikeoswego:
Those look like the correct files.

Try this:

In TWRP, flash xt1096-5.1-23.32-25-5-2_1.zip which you said worked but was requesting to do the update (which would have simply failed over and over.) Flash the GApps package and the debloat if you are using one of them. Wipe Data and Cache. Reboot the phone to system, answer No to any prompts to root or install SU that TWRP may show. Take it through the basic setup, your gmail account, etc. Don't bother to install apps yet. (Yes, skip the -2 version of the gpt and firmware zips, only go back and flash those if these steps don't work.)

If the above worked, go back into TWRP again and this time, flash XT1096-23.32-25-5-5-Firmware.zip and xt1096-5.1-23.32-25-5-5-Mod.zip and the debloat zip. You don't need to flash the GApps again. Do NOT wipe data or anything, just reboot the phone to system. It should start up after doing some maintenance and you'll be on the latest version.

Then, presuming the above worked, you can now use TWRP to flash SuperSU to get root. If you want Xposed, install that from TWRP as well.
[X 2014 Android Development] D.A.N.:
Sucessful Installation

Hello Mike,

Your instructions worked perfectly and now I am running the newest version. Thank you for the time you put into helping me and this rom. Have a great day.

John 3:16

D.A.N.
[X 2014 Android Development] mikeoswego:
Glad to hear it worked, thanks for the feedback!
[X 2014 Android Development] D.A.N.:
Reinalling Apps

Hello Mike,

Once I root phone again every time I restart it has to reinstall all apps. Do you know why the phone does this?
[X 2014 Android Development] mikeoswego:
You probably mean it does the optimizing apps thing everytime (rather than downloading and resintalling the apps?)

Which root are you using? Don't force systemless root, that might not work. I would recommend SuperSU v2.82 which you can download from this link: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
[X 2014 Android Development] D.A.N.:
Optimizing Continues

Yes Mike, your right, it optimizes the apps, all 78 of them. I tried your recommendation and it is doing the same thing. Phone was fine after all of your instructions, but I wanted root and this problem reoccurs every time. Is this normal for roms or just me?
[X 2014 Android Development] mikeoswego:
It is not normal for SuperSU to cause this kind of problem but not unheard of. Usually it is Xposed that causes strangeness with optimization. Here is a link to the latest service release of SuperSU, try installing that from TWRP and see if it helps. After installing, in TWRP use the advanced wipe option to wipe cache and dalvik cache only. (The dalvik cache is where all the optimizations created at boot are stored, if any one of them is corrupted, it will rebuild all of them.) In fact, you might just want to try the wipe of cache and dalvik cache before doing anything else. Another possibility is that one of your installed apps is causing some sort of problem, it can't be optimized and causes this cycle of repeated optimizations. That probably is not happening from any of the GApps but could for apps that you've installed from the play store or from other sources. If clearing the cache(s) doesn't help and the service release of SuperSU doesn't help, try running the phone with just GApps installed and if that works, try adding apps back in a few at a time and see what (if anything) causes the problem.

(Link to service release of SuperSU: https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip?retrieve_file=1)
[X 2014 Android Development] trimax84:
Not sure about this one. Sounds like you are using Google dialer though.... Try the image with the stock Moto dialer to see if it's the same result.
[X 2014 Android Development] mikeoswego:
This is due to the Google dialer and I'm now going to recommend that people not use that anymore. Another problem with the Google dialer is that your lock screen notification is just the tiny bar instead of a full/half screen notification. Messenger is still good and you can get that from the playstore.
[X 2014 Android Development] mikeoswego:
Notepad++ is the editor to use if you must use Windows to edit Linux/Android files.

Be careful when removing apps and you might want to list what you've removed. Some of those "bloatware" apps that don't seem to serve any function are actually used in less common situations and might come back to bite you. For instance you can't just remove all the things that start with "VZW". Our phone has plenty of resources so I doubt you'll see a performance increase by removing the bloat.
[X 2014 Android Development] JulesJam:
It should stop that pop-up about no data on a call at least if you have a 4G LTE signal at the time.
[X 2014 Android Development] contesauce:
Mike's first post includes xposed, but I didn't see you mention it here. Just to clarify this one in the link above does or does not have xposed? Also if I could throw my request hat into the ring and request this one image (if it does have xposed) without the gdialer? I want to test between the two and see what bugs or speed issues I'm running into. So far the gdialer seems to operate just fine for me, although pulling the dialer up seems to take a bit more time than the standard dialer. Then of course there is the "Data unavailable" while on a call thing that's kind of annoying.
[X 2014 Android Development] trimax84:
Yes, mine is built using Mike's as a base, so it contains Xposed.

So, to give a summary of the ROM in my link, it contains:

Mike's - Root, Tether, Xposed, BusyBox, SQLite3, Google Dialer, Google MMS, HDR fix

With my additions - AdAway ready, different boot animation, removed bloat, bootanimation memory leak fix

Please read my posts here and here if you're going to install my ROM. It has details on how to set up AdAway and some other useful information.

And unfortunately I have such limited time that I am unable to fill special requests. But I don't mind sharing any ROM I make for myself.
[X 2014 Android Development] contesauce:
Thanks, I'll check your image out, already have a symlinked adaway on my current image as well as the other features, only thing I don't have is operable HDR.
[X 2014 Android Development] KidCuda:
I really care about the memory leak module, I know some of you have installed it. Has anyone seen any improvement over the long term yet?
[X 2014 Android Development] trimax84:
The Xposed memory leak module or bootanimation memory leak fix?

I would presume you mean the Xposed one, in which case I have had it installed early on and didn't really notice a big difference with or without it. But I run it anyway since I figure it can't hurt.
[X 2014 Android Development] trimax84:
Anyone having an issue with sending MMS?

I'm on Verizon and think it might be related to the APN. Not sure why it would have worked in all other ROMs I've flashed with MoFo except for this most recent one. I'm reflashing now, but curious if someone with working MMS (send/receive) on Verizon could check some settings for me....

Go to your APN Settings (I think it's Settings -> More [under Network] -> Carrier Settings -> APN Settings)

What values do you have for:

Name:

APN:

MMSC:

MMS port:

MCC:

MNC:

APN type:

I've tried all sorts of things with apn-conf.xml and editing telephony.db via SQLite editor (For whatever reason, my phone doesn't allow me to manually add or edit the APN settings in the phone's 'settings' section, but yay for SQLite3 being included in this ROM!), but still having the issue. I have also tried manually setting APN configuration in the GoSMS Pro advanced settings section. And using the Google Messenger app or Google Hangouts did not work for me either.
[X 2014 Android Development] dudicle:
Mike - I attempted to create a new image based off of your version without Google Dialer/Google Messenger. The only change I made was replacing the stock hosts file with a symlink to a writeable hosts file in data/data/ . Much to my surprise (first time doing this), the image installed and booted. However, there was one major problem - the dialer didn't work (immediately crashed upon launching).

My last image was TotalX 1.1 which included the Google Dialer. Upon installation of my new image (based off of yours as mentioned above) I had to re-add the phone app to my dock drawer (just as I had to do when installing the Google Dialer version for the first time). Never worked - tried rebooting a few times. As far as I could tell, everything else worked fine.

Can you give me any direction as to how to get the stock dialer working again after flashing an image with the Google Dialer? I am completely new to this, so it's possible that I missed some step in creating the image, but the fact it booted tells me I didn't screw it up too bad. I used VirtualBox with Ubuntu, and more or less followed the process described in the post about modifying images over in the Turbo forums (sorry no link, I'm new).

Thanks again for the great, stable base!

Tom
[X 2014 Android Development] contesauce:
[MENTION=2921457]trimax84[/MENTION] here are my APN settings for Verizon. Something I used to overlook when I was setting up mms on other roms or 3rd party messaging apps is that verizons limit on mms messages are 1.2 mb unless it's increased, I heard they were going to make it 2 but not totally sure. When I used to use textra I had to set it to 1mb or it'd fail everytime.

This is copied case sensitive just in case.

Name: Verizon Internet

APN: VZWINTERNET

MMSC: http://mms.vtext.com/servlets/mms

MMS port: not set

MCC: 311

MNC: 480

APN type: default,dun,supl

Hope that helps.