yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
April 2016 security update

Verizon released a security update for the xt1096 (sorry, no Marshmallow..) The bootloader, modem files, kernel and system image were updated.

Build ID: LPES23.32-25-5-2 / Blur_Version.23.201.2.victara_verizon.verizon.en.US

xt1096-23.32-25-5-2_gpt.zip updates the bootloader

xt1096-23.32-25-5-2_Firmware.zip updates the modem firmware.

xt1096-5.1-23.32-25-5-2_1.zip is the updated rom and kernel.

The debloat and other zips from Post 1 & 2 still work with this version.

SuperSU v2.65 and Xposed v81 are preinstalled. If you dirty flash and your GApps support addon.d (OpenGApps do), you don't need to reflash them as the rom zip installer will save and restore them. I've tested this with both clean and dirty flash. Remember, a clean flash will take 4 minutes or so to boot up the first time. The bootloader update will cause mofo to quit working but I'd think nobody should care about that anymore. The new bootloader and modem firmware work fine with CM13 as well.

If you want the full unmodified system image, it's here: xt1096-full-stock-23.32-25-5-2.img.7z
[X 2014 Android Development] nitsua98:
Would there be any reason to update the bootloader?
[X 2014 Android Development] mikeoswego:
I honestly don't know why the bootloader (or the modem files) get updated in these security updates. In the past, when the only option to flash a new rom was using the Mofo exploit, replacing the bootloader would disable Mofo. Motorola would consider the Mofo exploit to be a security vulnerability so they patched it.

I presume there are further security issues that are possible via the bootloader so it was patched again. Having said that, it isn't necessary to update it to use the updated rom; I did go ahead and flash it and nothing bad happened so I would recommend updating it for whatever potential security issue is resolved. (I'm unlocked via Sunshine before Motorola was releasing unlock codes for the xt1096 so it won't cause you to lose your unlocked status whichever way you got it.)
[X 2014 Android Development] Cuoficr78:
What kind of changes were made to the ROM itself?
[X 2014 Android Development] mikeoswego:
Quote from Verizon:

"Software Version: 23.201.2.victara_verizon.verizon.en.US

The current software update gives you the most up to date Android™ security patch on your device."

The only mention I've found about this is here on Android Central: http://www.androidcentral.com/verizon-pushes-security-patch-update-moto-x-2014

So now you know as much as I do!
[X 2014 Android Development] me myself and i:
sp im having a.......peculiar??? issue i guess. Home and menu button wont act on the press........back button works seemlessly......but the menu and home button dont function, they vibrate on touch and long press on the menu button also vibrates that slightly longer vibration. Any clues and insight? thanks :)
[X 2014 Android Development] drewski_1:
i haven't seen this on mine.

are you running any mods that could change the button behaviors like Gravity Box XPosed module?
[X 2014 Android Development] me myself and i:
no change what so ever. it is like that on first boot. first boot without debloat and without gapps.
[X 2014 Android Development] drewski_1:
clean or dirty flash?

i think i saw something similar with a dirty flash on my N10 a couple months ago and a clean flash (wipe data in TWRP) fixed it.
[X 2014 Android Development] me myself and i:
clean flash.......wiped everything besides internal storage before flashing bootloader........rebooted recovery.......flashed firmware.......flashed rom......booted system. this was the current sequence. i had the same problem when i tried before the latest updates to the thread......im havign the same issues with other stock roms.
[X 2014 Android Development] mikeoswego:
So you are saying that everything is fine with a rom like CM12/13? That is bizarre! I'm not sure how to help since I've not seen the problem. I did a search and found that you are not alone in having this happen. Of course, some people resolved the problem by doing a factory reset; that didn't work for others.

One guy said: "Try setting your phone to have a security lock (Settings-->Security-->Screen Lock - I used pattern), then lock the phone using power button. Hit power button again, enter pattern, voila - fixed." And his buttons kept working after changing the lock method back to none. Definitely worth a try since its easy.
[X 2014 Android Development] me myself and i:
other things ive noticed, i got no internal storage when connecting it to my pc......had the same problems with other stock based roms. its a good thing i have a backup of the original to which i go back to where everything is working but severely bloated. one more thing.....i cant turn on developer options therefore i get no usb degugging.........
[X 2014 Android Development] mikeoswego:
Sorry, I don't have any help for you, I can't think of a good reason why you'd have the problems you're reporting..
[X 2014 Android Development] me myself and i:
i flashed the Tmobile stock rom.......everything works.......i have no idea, i have a feeling its firmware related but if it works im not going to look too much into it.....
[X 2014 Android Development] mikeoswego:
That's great! I'm surprised that works with Verizon but like you say, whatever works!
[X 2014 Android Development] enchilader:
Hey all, I'm wondering if anybody has tried this ROM with a carrier other than Verizon, particularly T-Mobile. I just ran into the T-Mobile store today to try a test SIM (I am going to Europe next month and they offer a much better international plan) and had some problems with SMS. While voice and data worked fine, it looked like I could only send text messages, but not receive them. [MENTION=5849464]mikeoswego[/MENTION] do you have any idea if the ROM could cause a conflict here? Looking for any input really, I've read in other threads (http://xdaforums.com/moto-x-2014/help/verizon-moto-x-2014-t-mobile-t3010369) that this should work fine so I'm pretty confused about what's going on
[X 2014 Android Development] mikeoswego:
According to T-Mobile's phone compatibility page: http://www.t-mobile.com/bring-your-own-phone.html?icid=WMD_TM_Q2BYODMRQR_67GDZ1LA2KV4836#compatibility, the XT1096 is not compatible with their network. The XT095 Pure edition is.

In this thread: http://xdaforums.com/moto-x-2014/general/guide-xt1097-to-xt1095-nextel-t2972693 it has been said that you can flash the xt1095 rom onto the xt1096 and it works but I don't have any personal knowledge about that.
[X 2014 Android Development] enchilader:
See it's odd that it says it's not compatible when I just went in there and almost everything worked fine. I feel like that is more laziness than fact, seeing as there are many sources saying it should work. I'll try switching over to the Pure Edition and see if that helps.

I know this is super off topic, but do you happen to know the best way to return to pure stock? (sans the bootloader unlock, I'll of course leave that unlocked as that should have nothing to do with it)
[X 2014 Android Development] mikeoswego:
Use a current version of fastboot and flash this system image: https://www.androidfilehost.com/?fid=24499762635999495 You will need to wipe data (or factory reset) as the paths for the GApps in the stock rom won't be the same as whatever GApps you installed.
[X 2014 Android Development] enchilader:
Thanks mike, you're being a huge help. So I imagine this will replace radio, modem, firmware, ROM and everything, but will this also replace my recovery?
[X 2014 Android Development] mikeoswego:
You can also take the system image I linked above, rename it and put it in place of the system.img file within the zip installer using 7zip.
[X 2014 Android Development] mikeoswego:
No, just the system image if you do it with fastboot. If you replaced the system image in the zip installer, the zip installer will reflash the kernel (boot image) and the system image. Recovery, modem, etc. is not touched.
[X 2014 Android Development] enchilader:
Hmm. Is it reasonable for me to assume that having a custom modem and firmware (those included in your ROM) might be what is causing the issue? Or is everything that you provide other than the system itself all stock, i.e. me flashing this system image is all I need to return to pure stock (as far as I can recall, your ROM is the only thing I have flashed (along with the firmware, GApps and everything else you provide)).
[X 2014 Android Development] mikeoswego:
The bootloader/modem/firmware updates that I provided are completely stock as if you had taken the most recent OTA from Verizon. The kernel (boot.img) in the installer zip is also stock. The full system image that I linked previously is completely stock; installing that will bring you as close to stock as is possible without somehow re-locking the bootloader.

The customized rom in this thread is somewhat to largely "debloated" with SuperSU root installed, other programs to support root added, and Xposed pre-installed as described in the first part of the first post. I doubt that those differences are causing a problem but I can't guarantee that.

Make a TWRP backup of data/system/boot, wipe cache & data, install the full system image, setup the phone without restoring any apps. Go to T-Mobile and try their sim again, if it works, great; reinstall your apps and carry on. If not, you can wipe cache, restore the backup and be back to where you are now.
[X 2014 Android Development] enchilader:
Thanks for the clarification. That's exactly what I plan on doing. Thanks again for all the help, people like you are the reason people like me keep coming back to XDA.
[X 2014 Android Development] enchilader:
Figured I'd come back with an update on what happened here. I have T-Mobile working now with your ROM on the XT1096. Basically, the demo SIMs that representatives might give you at the store generally are not fully capable e. g. they can't receive calls and have limited SMS. After all of my fretting I went back yesterday and a new rep said I just needed a SIM with a normal plan, which I tried and found to be fully functional.
[X 2014 Android Development] mikeoswego:
I wondered about demo SIMs being an issue but was derailed by the T-Mobile page saying the Verizon MotoX 2nd Gen wasn't compatible.

Glad to hear it's all working for you!
[X 2014 Android Development] jrbmed08:
It should be compatible because it has the right bands to get everything (2g, 3g, LTE). Oddly enough, when I lent my XT1096 to a friend on T-Mobile, it also didn't work. She didn't give me details on how and why, but I don't get it. It's sim unlocked by definition and I used it perfectly on Cricket (AT&T, not T-Mobile, but still GSM).
[X 2014 Android Development] gvbig:
Hey Mike, Great work and really appreciate all you do. I'm completely new to this process on Android. I'm using unlocked XT1096 VZW on Cricket (running 23.201.2 Build LPES23.32-25-5-2). So far I've got my bootloader unlocked through Motorola. Everything is working ok, but I don't need all the vzw bloatware. In addition to creating a backup of my factory ROM, that is all I'm looking to do in the initial stage (I'll explore the rest once I'm more comfortable with it). So, given all that can you please confirm/advise the must required files from below. For TWRP I'm going to be using twrp-2.8.7.1-victara.img. Thanks again.

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

xt1096-23.32-25-5-2_gpt.zip - TWRP zip to update the bootloader.

xt1096-23.32-25-5-2_Firmware.zip - TWRP zip to update firmware.

xt1096-5.1-23.32-25-5-2_1.zip - The factory based 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 "
[X 2014 Android Development] mikeoswego:
Your phone has been updated via the OTA if you have Build LPES23.32-25-5-2. That means that you do not need to flash the first 2 files in the list (...gpt.zip & ...Firmware.zip), they are already installed and wont' be affected by any future flashing of either the rom in this thread or CM13, etc. Installing them again wouldn't hurt anything, but they aren't needed.

Also, and I've just update the first post, the xt1096-5.1-debloat-keepconnect.zip may be preferable to the xt1096-5.1-debloat.zip since the keepconnect version also keeps files needed for full functionality of the Moto Gallery app.
[X 2014 Android Development] gvbig:
That sounds simple enough. I'll give it try and post the results. Thanks!
[X 2014 Android Development] gvbig:
Update 1: The rooting and TWRP install went well. ROM flashing on the first go didn't - first boot loaded fine but after the Setup Wizard got some update error. It made it to the main screen but no launcher at all. All it had was the top notification drop and bottom home buttons/menu. Tried to power off and restart but at restart it got stuck at "android starting apps" for long time.

2nd attempt at flashing much better results. Everything seem to be loading and running OK.

Now here are the things that I did differently:

1st attempt: Used - open_gapps-arm-5.1-nano-20160523.zip, Didn't connect to Wifi during the Setup Wizard

2nd attempt: Used - open_gapps-arm-5.1-full-20160523.zip, Connected to WiFi during the Setup Wizard

Questions:

Can I go back to TWRP and just install/flash open_gapps-arm-5.1-nano-20160523.zip or mini?

I've used debloat-keepconnect.zip as of now but isn't "Connect" from Moto going away anyway? Then why bother with it.

Thanks again for the instructions and reply.
[X 2014 Android Development] DjPorkchop:
I took my verizon xt1096 over to straight talk and it works great. However, I am still stuck full of verizon bloatware that is not needed and we all know disc space on this phone is at a premium. I badly need to work on this phone but am afraid to. it is my daily driver. I envy all you guys do and applaud you for doing so. Keep up the great work and making folks happier with their devices.
[X 2014 Android Development] drewski_1:
isn't the bloat in the System partition? so won't help your storage much to debloat
[X 2014 Android Development] DjPorkchop:
Im not real sure. Your most likely right. Im not real good at this stuff. I have an old Fascinate Im still rocking that I put 4.2.2 on and I managed to brick a GS3 (stuck in a boot loop) and I have my moto that I don't feel like fouling up. Its just on the 16 gb version the space available ... yuck!
[X 2014 Android Development] mikeoswego:
Ok, I looked into this and due to changes that have been made to the Open GApps packages, the minimimun package level that is going to work with this rom is the MICRO package; the NANO and PICO packages won't work at least for now. The reason is that unlike a custom rom like CM, etc. Motorola uses the Google Now launcher instead of their own launcher. The NANO & PICO packages do not replace the Google Now launcher with a version that is compatible with the rest of the GApps. (It is a mismatch between the version of the launcher pre-installed in the rom and the version of search that the launcher requires that is installed by the GApps package. Also the smaller packages don't install TTS (text to speech) except on 6.0 roms. Thanks for giving me the clues to track this down; I've updated the first post so that this is known to future readers.

Installing a smaller GApps package will not remove the already installed apps put in /system by the GApps installer. You would have to wipe system, flash the rom and then flash the smaller GApps package. There is another post that I'm going to comment on about the savings on our phone with different GApps packages that you might want to read

Finally, you are correct that Connect is being phased out by Motorola (if it hasn't already been shut down.) However, the first post implies that keepconnect debloat zip keeps only Connect. In fact it keeps that but it also keeps 4 "3c" apps. Those apps are required for the Motorola Gallery app to download the background music for the highlight reel feature. Without those apps, the Gallery will force close at every boot up "Gallery has stopped." Gallery continues to work as a photo gallery and if you don't care about the error message and don't use the highlight reel feature, then feel free to use the other debloat zip.
[X 2014 Android Development] mikeoswego:
It is correct that the debloat on a clean system install mostly saves space on the System partition and our phone has plenty of room for the super stock version of the GApps package, etc.

Where it can matter is over time as those apps are updated, the updates all go into Data taking away space available on internal storage for pictures, etc.

So, installing the minimal GApps can make a difference over time in how much space is used in data (unless the apps are installed from the Playstore anyway.) An interesting change that occurred with 5.0 and newer, is that installing a newer version of the GApps package does NOT recover that space used by updates in Data. It used to be with KitKat and older that you could reinstall the latest version of your GApps package and when you rebooted, Android would automatically "see" those newer copies in System and clean up the copies in Data saving space there, but not anymore. (The official reason for this is to prevent problems with apps that would be multi-part, with a portion being factory installed and then an update or extra features being in data and preventing a rom upgrade with new System apps from deleting the portion in Data.)

Osmosis has been working on a utility that replicates this process. As your phone downloads updates from the Playstore, his utility checks at every boot and attempts to move the update in Data into System and then patch the packages.xml file for the new locations. I've found it to be unreliable (not Osmosis fault and I haven't had time to look into it) and don't recommend it but if it would work, it could save close to a gb of space on data on my system. His thread for this and other utilities is here: http://xdaforums.com/showthread.php?t=2239421

For now, I just pretty aggressively keep things like pictures moved off the phone since it is only 8gb.
[X 2014 Android Development] Cuoficr78:
This interests me greatly. I'm running rooted stock rom, debloated from a fresh install (including removal of all the Verizon apps, as well as others I don't use). Even if I factory reset the device they don't come back. If they were still in the system data wouldn't the script reinstall them when the phone is restored to factory settings? I shall do some searching
[X 2014 Android Development] mikeoswego:
No, there is no backup copy of /system in the phone so the only way to restore them is to reflash the rom. All that the factory reset function does is delete everything in /data including the portion marked as /sdcard or internal storage.

In a stock phone, /system is *never* written to (except during an OTA update) and all personal info/data is in the /data partition. The point was that freeing up space in /system gives you no benefit whatsoever as far as available storage space for pictures, etc. since space in /system can't be used for anything else (at least not easily.)

Having said this, the real reason to debloat on a modern phone is for the slight increase in performance that you will have if unwanted system apps are not loaded at startup or to permanently stop potential spyware/annoyance apps installed by the carrier. (And, as mentioned previously, removing unwanted system apps does save space in /data over time since updates for those system apps goes into /data since /system is never written to.)
[X 2014 Android Development] jlenegan:
Moto x 1096 unlock

Motorola said that my phone isn't unlockable because it isn't a developer addition.The unlock tool doesn't work, says ineligible) Do most of you guys have a developer addition xt1096
[X 2014 Android Development] donslade:
To my knowledge there was no developer edition of the XT1096 released.

Motorola and Verizon are allowing the Verizon XT1096's to be bootloader unlocked. Call Motorola until you find a representative who knows about that and will provide the unlock code.
[X 2014 Android Development] mikeoswego:
Like donslade said, there was never a developer edition of the xt1096. When you say the unlock tool are you refering to this page: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and after logging in with your gmail account and the following the instructions on the next page:

Using Windows command prompt with the phone in fastboot/bootloader mode and connected to the PC:

fastboot oem get_unlock_data

and you got something that looked like this in response to the command:

(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000

And then you used notepad or whatever to change those 5 lines into something like this with no spaces:

0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000

And you pasted that line into the box on the unlock my device page and clicked "Can my device be unlocked?"

I just did this and the the page is prompting me to accept the legal agreement to have unlock code sent to my gmail account. So the tool is working. I'm going to guess that you're not getting the code entered correctly into the box (or the page was malfunctioning earlier.)
[X 2014 Android Development] Gooch4130:
No Voicemail Notifications

I rooted with the de-bloated install and have since not received voicemail notifications. I need to reinstall the default verizion voicemail app. The one on the play store is not correct. Anyone know where I can get the voicemail app that Verizon ships with the phone? Also, steps to installing would be awesome. Thank you in advance!
[X 2014 Android Development] mikeoswego:
Visual Voicemail is removed by the debloat zips. I've attached versions of the debloat zips that don't remove VVM.

To use them, you will reflash the rom in TWRP and then flash the appropriate debloat zip. If you used OpenGApps (or other GApps that support addon.d) when you first setup the rom, the rom installer zip will backup then reinstall them, you don't need to reflash them (though you can if you want.) If you flashed any other things you may have to reflash those as well if they don't support addon.d. Do not wipe anything in TWRP before doing this unless you want to start fresh.

Alternatively, if you don't want to use Visual Voice Mail, you can call Verizon customer service and tell them you don't want to use VVM anymore but aren't getting the notification of new voice mails in your status bar; there is a switch they can flip on their side to restore the old style voicemail notification which was automatically disabled when VVM was used the first time.
[X 2014 Android Development] Gooch4130:
Steps worked perfectly. Thank you as always! I have voicemail notifications again =).
[X 2014 Android Development] rotorbudd:
Mike,

I turned my Moto X over to my wife after convincing her to give up her iPhone 5c. You would have thought that I'd given her a diamond necklace! She likes it sooo much better than the iThing.

Do you plan on doing any security updates on this ROM if Motorola does a release? Also any idea if there will be a MM for this phone that still has the Motorola apps?

Thanks for all the effort you've put into this.