yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
This ROM is for xt1096 models used in the US on the Verizon network. I know that some people use the ROM in other countries on other carriers but they are still using the xt1096 model. I don't know if it would function on the xt1092 or not. I would look for an xt1092 rom. The next nightly of CM 12.1 to be posted in a few hours will include xt1092 support. That thread is here: [ROM] [5.1.x] Official CM-12.1 nightly releases
[X 2014 Android Development] tacosrdelicioso:
Yeah. It goes in spasms. It'll be okay for hours and then it'll freak out. :/ maybe we'll get a baked in version so we can be free from these afflictions
[X 2014 Android Development] dubluv17:
I'm getting the low storage error and I'm having a hard time deleting those /data files. I'm unable to install anything from the play store because of it and ES Explorer isn't liking the root. I set SuperSU to grant and it says it grants, but then ES explorer says the feature failed to run. Is there any other way to delete those files? Maybe through ADB? Thanks in advance for the help.
[X 2014 Android Development] JulesJam:
I would flash back to stock and then start again from the beginning.
[X 2014 Android Development] mikeoswego:
Like JulesJam said, its probably easiest to just flash back to stock (or one of the mofo images without Xposed) and start over.
[X 2014 Android Development] dubluv17:
For the record, I flashed back to stock, installed root checker and root explorer, then flashed the rooted image. Then I had to set SuperSU to 'grant' default before opening root explorer to delete the /data files. Doing this worked and now I'm good. Thanks!
[X 2014 Android Development] mikeoswego:
Thanks! I've updated the first post telling people that they should flash one of the btdownloads7 images first to get root so they can complete the deletions in /data/dalvik-cache without problems.
[X 2014 Android Development] ry_t:
just flashed the first img and it says the Play Store isn't installed and it says I'm running low on storage
[X 2014 Android Development] mikeoswego:
From the first post:

You need to flash an image without Xposed from here: http://xdaforums.com/showpost.php?p=60537982&postcount=1 Then, after rebooting with one of those images follow the steps in the first post in this thread to properly install an image with Xposed.

You can try to delete the 2 folders in /data/dalvik-cache and reboot, otherwise, you'll have to flash the non-Xposed image as written above.
[X 2014 Android Development] d33dvb:
From what i hear we can remount in rw, then make changes, but the changes dont stick on reboot. To workaround this so we 'keep' system changes after reboot, could we not make a directory in /sdcard, then on boot up, remount in rw, push the files to system? Then have a script to push all /system changes to /sdcard/system changes on shutdown?
[X 2014 Android Development] mikeoswego:
Currently there is no way to write to /system except when it is not mounted; like modifying the /system image before flashing it with mofo. The locked bootloader prevents the phone from ever writing to /system except in the case of mofo writing a whole new image (or an authorized ROM image from the factory.) Yes, you could have an app or script that "wrote" things to /system that, as you understand, won't stick after a reboot. Fortunately there are very few things that actually need to write to system on a regular basis and those (like adaway) have been made workable by creating a symlink on the unmounted /system image to somewhere in /data which is writeable.
[X 2014 Android Development] JulesJam:
I believe he is talking about doing this:

http://xdaforums.com/showpost.php?p=59686353&postcount=136

then making system changes and on power down, saving the system changes on the sdcard, then on reboot, having a script do what is in that link above and then also retrieve the saved system changes from the sdcard and redo the system changes. At least that is what I took what he was saying to mean.
[X 2014 Android Development] mikeoswego:
Yeah, I didn't say it couldn't be done. Maybe I'm just an optimist in thinking that we'll get a bootloader unlock soon and there won't be any further need for work arounds!
[X 2014 Android Development] JulesJam:
I am not an optimist, but for my use of this phone, mofo works fine. Thanks again for all of your effort in creating these images!!!!
[X 2014 Android Development] JulesJam:
Why do people want Google Dialer and Google Messenger to replace the stock dialer and stock MMS?
[X 2014 Android Development] fakieskr8333:
Not sure about Messenger since you can just switch apps but i personally like being able to search for businesses and the like in the dialer with the google dialer.
[X 2014 Android Development] mikeoswego:
I like Google Dialer because of the Google caller ID. Verizon probably had the Google caller ID stripped out so they could sell their monthly Verizon caller ID service. Google caller ID isn't earth shattering but they do seem to have a lot of outbound 800 number centers in their listings. So instead of just a generic 800 number on the incoming call display, it will say CitiCard Fraud Prevention or Progressive insurance, etc. Other people like the business search on outgoing calls like mentioned by [MENTION=3364035]fakieskr8333[/MENTION].

Messenger is just Google's material design version of the stock mms app. Colors of your conversations are based on the contact image associated with it or by your choice in a palette chooser. Swipe left or right to archive a conversation (archived threads can be found via the Archived option on the app menu or through the search function); tap and hold to archive, mute or delete a conversation. When you're viewing an SMS thread you can tap on a contact picture to bring up more details about the individual. Tap and hold on a single message to copy, delete or forward it, or to see the details of the message. When you're composing an SMS you can tap on the paperclip icon to add an image, video clip or voice recording to your message.
[X 2014 Android Development] JulesJam:
thanks, mike!!

Do you or anyone else know why I may be having trouble with group messages from iPhone users? I used to receive them fine but now, when my family members include me in a group text (they are all iPhone users), I can sell all the texts from the person who initiated the conversation but not from the other iPhone users. This never happened on kit kat so I think it may be a lollipop issue. Does anyone else experience this?

Obviously this is an iMessage issue but it didn't occur on kitkat.
[X 2014 Android Development] mikeoswego:
I wonder if Apple changed something in iMessage about the same time as KitKat was coming out. I found this: https://support.apple.com/en-us/HT202724 and it says you won't receive copies from other participants if using mms and not iMessage:

"If you send a message to multiple people and at least one person isn't using group messaging, an individual message will go to each recipient using either SMS or MMS. Only the original sender will get any responses to these messages, in separate message threads."

It also says: "To use group messaging with MMS, you need a plan from your carrier that allows sending MMS. Carrier messaging rates may apply." Do the people with iPhones sign up for plans without MMS since the iPhone apparently doesn't use the sms/mms system inherently for the iMessage app?
[X 2014 Android Development] JulesJam:
thanks, yeah that seems to be the problem. I will try to get them to turn off iMessage, we have unlimited texts so no need to use it.
[X 2014 Android Development] neh4pres:
anyway you can include an ad block in your image?
[X 2014 Android Development] mikeoswego:
Stagefright patch xt1096-5.1-23.32-25-5_4

[MENTION=4307096]redwings73[/MENTION] provided me with the factory update zip file for the stagefright patch and I've made TWRP flashable versions available for download.

First, the update patched some modem firmware files (but not the baseband.) Those files should be updated first. The xt1096-5.1-23.32-25-5_2.zip includes both a new boot.img (kernel) and system image. The ROM has tether enabled in build.prop, BusyBox, SQLite3, zip, aapt, SuperSU, Xposed framework and Xposed installer already installed.

The update should go like this, make a TWRP backup first then still using TWRP;

Install the modem firmware zip available here: xt1096-23.32-25-5.modem.zip.

Install the new stock based image zip available here: xt1096-5.1-23.32-25-5_4.zip.

If you are using TK GApps, the addon.d script should preserve them unless you wiped system. Other GApps may need to be reflashed if they don't support addon.d. Might want to flash them just to be sure.

All of the debloat, Viper4Android, Emoji, etc. zips from post 2 are unchanged and will continue to work with this updated version.

After all the zips flash, use the wipe cache/dalvik button before rebooting. Don't reboot until you have flashed all the zips you are going to install.

This rom already includes SuperSU, don't flash it again to avoid problems. Make sure you have a backup if you have some reason to flash a different su.

Xposed is already installed in the rom. You don't need to flash it although it is probably safe to do so.

Mofo users scroll down a couple posts for your update.

I haven't been able to get Android Pay to allow setting up a credit card, there is a security check that is failing even with the ROM in mostly stock form. This is either caused by the unlocked bootloader or that the phone sees the software as modified.

Only flash the modem.zip once, that update will be permanent. If you try to flash it again, it will find the files are already updated and fail.
[X 2014 Android Development] redwings73:
Awesome... Thanks! I really hope a Android Pay fix will be available.... It's driving me crazy.
[X 2014 Android Development] mikeoswego:
Stagefright patch xt1096-5.1-23.32-25-5-mofo

Here are the instructions for mofo users to update to the latest version with the Stagefright patch:

The archive listed below is for people who are already running 5.1 on their phone, if you are still on 5.0, you must update to 5.1 as instructed in the first post.

The archive contains a patch folder with these xdelta3 patches:

xt1096-23.32-25-5-mofo--mofo-cf-de.patch - debloats while keeping CF.lumen

xt1096-23.32-25-5-mofo--mofo-de.patch - debloats

xt1096-23.32-25-5-mofo--mofo-de-noxp.patch - debloats & no Xposed

xt1096-23.32-25-5-mofo--mofo-v4a.patch - adds Viper4Android

xt1096-23.32-25-5-mofo--mofo-v4a-cfde.patch - adds Viper4Android, debloats, keeps CF.lumen

xt1096-23.32-25-5-mofo--mofo-v4a-de.patch - adds Viper4Android and debloats

In addition, the following patches are attached to this message:

xt1096-23.32-25-5-mofo--mofo-ex2.patch - Restores stock email and Exchange2

xt1096-23.32-25-5-mofo--mofo-noxp.patch - Removes Xposed only

The archive contains a fastboot folder. The files in that folder need to be applied to the phone using fastboot before mofo flashing the new image. This only needs to be done once. Use the following commands:

fastboot flash boot boot.img
fastboot flash fsg fsg.mbn
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase DDR

# Note the capitalization of DDR in the last command

Here is the archive: xt1096-23.32-25-5-mofo-pkg.7z
[X 2014 Android Development] eric1743:
I'm unable to get the xt1096-23.32-25-5-mofo image to boot. I flashed modem, fsg, and boot. Mofo flashed the image on a clean phone, and I only get as far as the static Motorola powered by Android image in the boot sequence. Flashing the xt-1096-5.1-v3.1g image works and boots fine.

As a separate request would you be able to offer an image or a patch without xposed? I am trying to run sunshine but the program hangs up when it detects xposed framework present.
[X 2014 Android Development] mikeoswego:
Sorry you had trouble with the mofo files. There was a problem with the files in the archive and I've uploaded a corrected version. Post 783 has been updated for the fixed archive which now includes a patch to remove Xposed.

Here is the link for the fixed archive: xt1096-23.32-25-5-mofo-pkg.7z

I thought that the newer version of Sunshine worked even with Xposed installed. I don't remember needing to remove Xposed but maybe they've changed that. As I mentioned, the fixed 23.32-25-5 archive includes a patch to remove Xposed. I'm also attaching a patch here for v3.1g to remove Xposed for anyone that might want that.
[X 2014 Android Development] drewski_1:
I didn't need to remove Xposed for Sunshine either, but there have been a few newer versions of Xposed released.

Maybe Sunshine needs some adjustments for those?
[X 2014 Android Development] jrbmed08:
Same here, didn't need to remove Xposed to use SunShine. At first SunShine said I needed a ROM that was closer to stock, but then they updated the app and it worked perfectly without any modification.

Thanks again Mike - flashed your Stagefright patched image via TWRP and it's working great!

If you could figure out how to get VoLTE working, I'd kiss your feet. But I think that's something Verizon has to enable on their end too.
[X 2014 Android Development] mikeoswego:
Yeah, that was my experience with Sunshine as well.

When I saw that some of the modem files were being updated, I thought it might have to do with VoLTE but no such luck. It's weird that build.prop has a line enabling VoLTE even before this most recent update!
[X 2014 Android Development] rhpot1991:
I am getting storage space running out messages after updating via TWRP, even though I have 3.5GB free. Any ideas? I tried wiping cache and dalvik again, didn't help.
[X 2014 Android Development] mikeoswego:
In TWRP, try using the file manager and delete the folder /data/log
[X 2014 Android Development] rhpot1991:
Doesn't appear to exist, I wonder if that is why.
[X 2014 Android Development] mikeoswego:
No, it doesn't have to exist. I had this happen once and am trying to remember what I did to fix it. Again in the TWRP file manager, take a look and see if after using the wipe cache/dalvik button, are the folders in /data/dalvik-cache removed (or at least empty) and if that /cache is empty. If not, try using the advanced wipe function, then select dalvik and cache. Then check again with the file manager.
[X 2014 Android Development] rhpot1991:
dalvik is removed. cache has a recovery folder with recovery.fstab and storage.fstab remaining, and a lost & found which is empty.

---------- Post added at 05:37 AM ---------- Previous post was at 05:33 AM ----------

It optimizes apps on boot too, but flies through it. Not normal optimization.
[X 2014 Android Development] mikeoswego:
Presuming you have a backup (or make one now) try wiping /data and see if the storage space messages go away. If they do, it proves that the ROM is ok and something has gone wrong in your /data . It may be simplest to just start over at this point and I think that is what I did but then later read about the /data/log problem and wondered if I could have used that..
[X 2014 Android Development] rhpot1991:
I do get an "Unable to mount storage" error in TWRP constantly, I assumed it was my OTG drive not being plugged in. I backup there, but then install from downloads. Got that message on the past installs and everything worked fine.
[X 2014 Android Development] mikeoswego:
Yes, that is exactly what I saw. Ok, if you still have this problem after the wiping /data test, I figured this out the other night when I was assembling the new image but have slept since then.
[X 2014 Android Development] rhpot1991:
I took a backup first so I may just restore from that. Oddly I'm seeing 2 backups with the same date in here, and neither is today. Going to investigate that some before I continue.
[X 2014 Android Development] rhpot1991:
Advanced wipe didn't remove those. I already started a restore and it is doing a lengthy app optimization now, so I should be back up and running. I'll try again tomorrow then, hopefully it goes better.
[X 2014 Android Development] mikeoswego:
I misread your post, those files do belong in /cache/recovery.

When you flashed the 23.32-25-5 rom did you install SuperSU and Xposed? Did you debloat or add Viper, etc.? It should have worked no matter which options you chose, just trying to pin down what happened.

After your hopefully successful restore, did the can't mount storage message go away in TWRP?
[X 2014 Android Development] mikeoswego:
23.32-25-5 full stock image

Someone asked for an unmodified system.img file, just as it would appear after doing an OTA of the Stagefright patch. I had to create that in the process of making the TWRP and mofo image files and I've uploaded it for anyone who wants to "roll their own." This file would be flashable with mofo if someone wants to try validating a credit card in Android Pay with a bone stock system image. Warning: This might leave a lot of junk in /data from all the stock apps, the differences between the stock GApps and whatever GApps you've installed might cause conflict. Make a backup first! If it turns out that Android Pay will validate cards (and then still function for Tap and Pay after going back to a rooted image), I'll make a TWRP flashable version of this image.

Here is the file: xt1096-full-stock-23.32-25-5.img.7z
[X 2014 Android Development] mikeoswego:
I've been able to replicate the problem. If you were to look in /data/dalvik-cache/arm, you would find there aren't any files there. If you install Xposed, the problem is resolved.

For some reason, the ROM is not able to create the dalvik files while the version of those processes that Xposed installs do work. The lack of the dalvik files causes the out of memory errors. I remember now that I had this happen when I'd made a mistake installing Xposed into the mofo version of the new rom. I don't see any obvious reason for this problem to exist at the moment but need to put some charge back into my phone before working on it some more.
[X 2014 Android Development] tjohnstone3:
Do you still happen to have the version of sunshine you used that didn't require you to remove xposed? I was going to run sunshine today but ran into the xposed issue and didn't want to trial and error downloading/installing/running the older versions to find which one worked.

Thanks in advance.
[X 2014 Android Development] joshnat:
I received the OTA message before coming here to get the flashable zips. The message said it was downloaded and ready to install. Does anyone know where it was downloaded so I can delete it, and how to disable future OTA's?
[X 2014 Android Development] jrbmed08:
Just combed through my phone and it looks like I deleted it. Sorry! Maybe [MENTION=5849464]mikeoswego[/MENTION] still has it considering we had the same experience.
[X 2014 Android Development] tjohnstone3:
No problem, thanks for looking. Doesn't seem like they even have the old downloads available.

Hopefully can get some time tonight or tomorrow to mofo the version w/ out xposed and just use the newest one. Want to get this done asap so I don't accidentally install the newest OTA.

edit: will just freeze the OTA updater
[X 2014 Android Development] redwings73:
It's in /cache...and you can prevent future OTA's by freezing the MotorolaOTA (7.1.0??) system app with Titanium BackUp.
[X 2014 Android Development] mikeoswego:
I don't have that Sunshine apk on my phone anymore but I might have a backup. I'll look in a little while.

Definitely don't take the OTA. I didn't mention this before but the Stagefright OTA also included a gpt.bin file to flash. That's the bootloader and anyone who flashes that would lose mofo if they still have it, lose Sunshine if they have that, and probably be unable to use Sunshine afterwards.
[X 2014 Android Development] mikeoswego:
I'm pretty sure that app is needed for Connect to work properly. That's why it is removed in the debloat.zip but not in debloat-keepconnect.zip. Since I don't use Connect and use debloat.zip, that probably explains why I didn't get a notification for the OTA and it never showed when I checked in System Updates.
[X 2014 Android Development] redwings73:
I think you're correct...I did not freeze the MotorolaOTA before I used Connect. Now that it's frozen, I can no longer use Connect....
[X 2014 Android Development] mikeoswego:
xt1096-5.1-23.32-25-5_2.zip

What a nightmare.. It turns out there is some kind of issue with what Motorola has done with this ROM. It isn't designed to have the system apps updated (which wouldn't happen in the "expected" usage scenarios. When there are non original apps installed into system at first boot, the rom refuses to create the dalvik-cache files leaving the phone unusable. If Xposed is installed there is no problem because it replaces the art/dalvik-cache mechanism and it isn't picky and just works.

I found it was possible to use the new ROM without Xposed if only the stock apps where installed (they are all odexed and don't get dalvik-cache entries.) I also found that if the rom was booted after wiping and allowed to get to the setup screens, you could then go back into recovery and flash the GApps, reboot and then it would properly optimize those apps. Then, it was possible to go back into recovery and restore the backup of /data avoiding the need to set everything up again. What a mess and, again, this is new with the stagefright patched rom.

Since the whole point of this rom is to have root and root is required for /system to be read/write, I've decided to put SuperSU back into the rom image. Since it can be such a disaster if someone forgets to flash Xposed, I've also put the Xposed framework and installer back into the ROM. I'll post a TWRP zip in a while that will remove Xposed for those who really don't want Xposed on their phone.

In the process, I discovered another problem with the addon.d support. Everyone should look in /system/addon.d and make sure there isn't a file named 99-SuperSU or something similar. The only way this file would exist is if you went into the SuperSU app and selected the OTA survival option. Unfortunately, when that is run when flashing the rom, it breaks things and the phone will hang at the initial boot logo. The _2 version won't run the file if it exists but you won't be protected until after _2 is flashed. You can also just wipe system before flashing to avoid any problems.

While I was in there, I tried to restore the stock email and exchange2 apps since a couple people have asked about that. It turns out that Moto put the email app in a location that isn't compatible with TK GApps (and probably most others) and it fc's if placed in the normal location.. So it isn't practical to put it back into the ROM. I will post another TWRP zip that will restore the stock email and exchange2 apps for those who aren't satisfied with the nearly identical GMail implementation.

So, I'll update the first post but I'll remind here that with this version it is no longer needed to flash SuperSU, it may break things if you do. It isn't necessary to flash Xposed either but it probably won't hurt anything if you do. Take a quick look in /system/addon.d for a file named 99-SuperSU or similar and delete it, most of you won't have this file. If things are working for you now, there is nothing new and you don't have to upgrade at this time.

Here is the new version: xt1096-5.1-23.32-25-5_2.zip
[X 2014 Android Development] jrbmed08:
That sounds like a giant pain in the ass for you to sort out. Thanks.

Considering I wiped system before flashing the stagefright patch and don't see any superSU file in the addon.d directory, I should be fine, right? Nothing else to do?
[X 2014 Android Development] mikeoswego:
Yes, you should be in good shape!
[X 2014 Android Development] mikeoswego:
Mail/Exchange2 & Remove Xposed zips

A couple more TWRP zips are available:

xt1096-5.1-Mail-Exch2.zip - Restores stock email & exchange2, removes exchange3. Flash

after

flashing GApps.

xt1096-5.1-Rem-Xposed.zip - Removes Xposed from ROM, use only

after

ROM has been started and setup is complete