yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] rotorbudd:
Will this work on a freshly unlocked and rooted XT1096?

I'm on CM13 right now but would like to get the Motorola apps back.
[X 2014 Android Development] neh4pres:
Is there anyway to use a script to compare and show the deference between the 2 kernels and 2 roms? Or has too much changed between lollipop and mm kernel wise?
[X 2014 Android Development] drewski_1:
yes, it will.
[X 2014 Android Development] rotorbudd:
Well I tried by doing a complete wipe, loading xt1096-5.1-23.32-25-5_4.zip and the TKgaps micro package. All I have is a continuous reboot. Back into TWRP and load the backup, no problem with it.

Any suggestions?
[X 2014 Android Development] mikeoswego:
I need to update that first post, TKGApps haven't been updated for months now. OpenGApps work identically and would be the ones to use for a fresh, clean install. http://opengapps.org/ There is no need to update GApps unless doing a clean install with Lollipop and Marshmallow roms (unlike KitKat and older roms where there was a benefit.)

You said a complete wipe, does that mean you did wipe Data as well as System and Cache in the advanced wipe menu of TWRP? Had you already taken the OTA with the Stagefright patch? If not you would need to flash the xt1096-23.32-25-5.modem.zip file from post 781

If you are just wanting to root or install Xposed, you don't really need to use this ROM, you can get root by using this SuperSU installer: http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

And if you want Xposed, use this installer: xposed-v79-sdk22-arm.zip

Just make sure to keep your original TWRP backup and you can restore just System to get back to where you were before rooting and/or adding Xposed.
[X 2014 Android Development] rotorbudd:
Thanks for the reply. You seem to be one of the most helpful developers on XDA. That's one of the reasons I wanted to try this Rom.

I wiped system, Data, and Cache twice before loading the zips. All I got was the unlocked bootloader message for aprox. 3 minutes, then a reboot to the message again.

I'll try the other gapps and redownload the ROM and check the MD5.

I bought this phone on Swappa last month and it already had 5.1 loaded. Do I need the Stagefright zip?

Thanks again for the help.
[X 2014 Android Development] mikeoswego:
If the phone has the Stagefright update, it will say LPE23.32-25-5 in the Build number at the bottom of the About phone screen. It won't hurt to flash the modems.zip, it will fail harmlessly in TWRP if it isn't needed.

It is normal on this ROM to see 4 minutes or so of apparent inactivity at the first boot on a clean install but it shouldn't reboot again by itself.

I'm looking at a few tweaks to how the installer zip is currently assembled to see if that might fix the problem.
[X 2014 Android Development] mikeoswego:
xt1096-5.1-23.32-25-5_6.zip

I've put together a new flashable zip that will hopefully fix problems with boot loops for people flashing this rom for the first time after unlocking their boot loader. The main change is in how the system image is stored in the installer zip. If I'm right, there has been a security issue with the file structure due to how the files were stored. Hopefully, [MENTION=4787586]rotorbudd[/MENTION] will be a tester for this new format and report back. If successful, I'll update the first post to point here.

First, this ROM needs the latest modem firmware. I've made a new TWRP flashable zip for updating the firmware that will work no matter what is on your phone now. It will update the fsg and NON-HLOS partitions. It won't hurt anything to flash this more than once, but once is enough. Here is the firmware update: xt1096-Stagefright-Firmware.zip

The system image in this installer zip has been updated with SuperSU 2.52, Xposed v79, and Busybox v1.24.1-Stericson. These are minor updates and no one should feel the need to upgrade their installation; "if it ain't broke, don't fix it."

The new TWRP flashable image is here: xt1096-5.1-23.32-25-5_6.zip

In addition, there are new debloat zips attached. They are just like previous versions of the debloat scripts but they do not remove apps that are needed for gestures, attentive display, and are needed by gallery to stop FC's at startup. (One of those apps no longer debloated is an app with OTA in the title, this has nothing to do with OTA system upgrades.)

Here is the list of apps deleted by the debloat zip, the keepconnect version does not remove Motorola Connect:

ECID_VZW_Victara (Verizon Caller ID $)

GoogleHindiIME

GooglePinyinIME

iWnnIME

KoreanIME

com.gotv.nflgamecenter.us.lite

VZMessages

BodyGuardApp (Alerts)

Verizon Cloud

Verizon CloudSetup

Entitlement

MotorolaConnect

MyVerizon

VVM3 (Visual Voice Mail $)

Latest version of CM's Trebuchet launcher and AudioFX sound mixer are in the xt1096-5.1-CM-20160121.zip
[X 2014 Android Development] rotorbudd:
Thanks for the update. I'll give it a try this evening and let you know how it goes.
[X 2014 Android Development] mikeoswego:
I've updated the first post to make it easier for people who are unlocking via Motorola's unlock page to install this ROM including links to the latest version.

The details for those already using the ROM were posted yesterday in post 1009.

I've added a new version of the CM Trebuchet and AudioFX installer with the latest versions of those apps: xt1096-5.1-CM-20160121.zip
[X 2014 Android Development] rotorbudd:
So, I was going to flash this and when I tried to go into recovery all I got was the TWRP splash screen. Tried to enter from bootloader same problem. Tried to reload TWRP from app, got fail message. Tried to reload from fastboot "fastboot flash recovery twrp.img" seemed to take but same frozen screen. Updated CM13 with their recovery and I can access CM recovery no problem.

But should I try to flash the xt1096-5.1-CM-20160121.zip and other needed zips in CM, or should I fix TWRP first?
[X 2014 Android Development] mikeoswego:
I've seen reports by others about TWRP getting stuck at the splash screen.

I'm attaching a zip to this message that contains two different versions of TWRP. One is by romracer from last summer, the other by invisiblek from last month, they are identified by the file name. If you find that one of these works, I'll update the info here to point people to the one that works (they all work for me..)

The TWRP app has never worked right for me, I always use fastboot to flash it.

In you internal storage folder, there is a folder named TWRP; you can try deleting that to see if corruption there is causing the problem.

I've never used the CM recovery but it should work. It does not offer the crucial backup and restore functions that TWRP has. The CM recovery is more designed to be their own solution for OTA updates without relying on outside software like TWRP.
[X 2014 Android Development] rotorbudd:
I'll try them both.

When I originally rooted this phone I had to boot TWRP and install SU from there.

Strange thing is, TWRP worked until 1/21 nightly.

fastboot flash of both .img files worked for me.

I can enter recovery from ROM or bootloader.

Thanks for the help,, again!!
[X 2014 Android Development] mikeoswego:
Thanks for the feedback, I've added the info to the first post.
[X 2014 Android Development] rotorbudd:
Version of TWRP?

I wonder if this was the diff.?

I had been using 2.8.7.1 and both of the ones you furnished were 2.8.7.0
[X 2014 Android Development] drewski_1:
hmm. i'm using 2.8.7.1 AOK.

maybe your img file got corrupted somehow?
[X 2014 Android Development] mikeoswego:
Yes, both 2.8.7.0 and 2.8.7.1 from the official website work for me. Multiple people have reported the splash screen freeze in other threads so it is a real thing. Many people recommend the the 2.8.7.0 version by romracer which I included in that zip. (He is the guy who posted the first versions of Xposed for Lollipop with permission from rovo89.) The other version in that zip was by invisiblek, an XT1096 user on Verizon and one of the maintainers for the CM13 victara version. Some of the problems may be related to device encryption which I don't use for performance reasons.
[X 2014 Android Development] rotorbudd:
Could be, but I D/Led the file at least twice. Both were from the TWRP site tho.
[X 2014 Android Development] rotorbudd:
At Last

Got the Rom loaded at last.

The first time I tried to load it I forgot to add the superSU zip to the queue. When the ROM just showed unlocked screen. Sat there watching it for 15 min.

Then the lightbulb came on when I remembered the CM ROM has an internal root. Maybe add a note to the install instructions for dumbasses like me!

Everything is working great. Now to go through all the Exposed modules.

Thanks for all the help getting this ROM running.
[X 2014 Android Development] mikeoswego:
Ok, so you installed the xt1096-5.1-23.32-25-5_5.zip rom and it still got stuck at the boot logo. Then you included the SuperSU in the zips you flashed and everything was good? You should not have needed that as SuperSU is pre-installed in the ROM. However, this is a crucial bit of information, that installing SuperSU over the pre-installed version fixed things; that points directly to a problem with how I'd set up the pre-installed SuperSU and I've corrected that with yet another version: xt1096-5.1-23.32-25-5_6.zip

I've updated the OP and the other posts that reference the _5 version to to this _6 version. It won't hurt anyone to update, but if things are working for you now, you aren't going to notice any difference with the _6 version. This hopefully, fingers crossed, will finally fix this hang at first boot that some people have experienced.
[X 2014 Android Development] rotorbudd:
I've got a backup now. Want me to try with the original rom without su to m:ake sure that's the problem?
[X 2014 Android Development] mikeoswego:
I don't like asking you to go through all that work and sometimes, once people get by the problem, it doesn't reoccur. I'm not able to reproduce this problem, the rom has always installed and worked for me but I probably don't have the same combination of bootloader, partition table that you have (since I started with mofo and unlocked with sunshine and have deliberately not updated the bootloader, etc.)

If you do have time and want to help, try wiping system, data, cache and then installing the _5 version of the ROM without installing the SuperSU zip. If it still hangs at the boot logo, try installing the _6 version (again without the SuperSU zip.) If it works then, that would be confirmation that this problem is finally resolved for new people in the future! (I completely understand if you don't want to do this experiment.)
[X 2014 Android Development] rotorbudd:
It's no big deal. I've done so many backup/restores it's almost automatic. All the old files are still on the sd card.

I'll give it a try and let you know.
[X 2014 Android Development] rotorbudd:
OK, I gave both a try.

The -5 zip loaded fine without adding the SU zip.

The -6 zip did the same.

When I originally rooted this phone I loaded CM13 which doesn't require a SU zip. Could this have anything to do with the -5 zip not booting the first time?
[X 2014 Android Development] mikeoswego:
Thanks for going through the effort. I was afraid the results would be inconclusive. Certain people have had this problem with the rom refusing to boot, something gets changed, the problem goes away and can't be reproduced. I doubt that having loaded CM13 first caused a problem, I've gone back and forth between this ROM and CM12/13 dozens of times.

I still have fairly high confidence in the change to the SuperSU pre-install being the fix. The change involved one of the very first things the ROM does at boot up so it all makes sense to be the cause. Time will tell!
[X 2014 Android Development] redwings73:
Hey Mike. I haven't had a random reboot in some time.... Basically since I messaged you last. The last couple of days there has been a number of them and I just got a bug report generated by the system, which is attached.

I have no clue how to read it, but thought someone here could help. http://bit.ly/1ND8gee
[X 2014 Android Development] kaktusmaier125:
Hi if i need just to root stock 5.1 how to make it?

Is possible to root just flash SuperSU via twrp or it need to flash modified boot.img?
[X 2014 Android Development] AGISCI:
After you flash twrp, open twrp. Then from twrp reboot, twrp will ask if you want to root the phone, say yes. Easy.
[X 2014 Android Development] mikeoswego:
There's a lot there, unfortunately nothing jumps out. You will probably have to try disabling various apps to see if you can figure out what is causing this for you. :(
[X 2014 Android Development] drewski_1:
try and grab the "/proc/last_kmsg" after the reboot.

it should have the kernel log right before the reboot and could shed light on what caused it.
[X 2014 Android Development] kaktusmaier125:
Is xt1096-5.1-23.32-25-5 build latest or xt1096-5.1-23.32-25-5_6.zip?
[X 2014 Android Development] mikeoswego:
xt1096-5.1-23.32-25-5_7.zip is the latest TWRP flashable stock based image. It has SuperSU, Xposed, BusyBox, SQLite3, etc. preinstalled.

xt1096-full-stock-23.32-25-5.img.7z is the full, unmodified xt1096 system image with the Stagefright patch applied. This image can be flashed with mfastboot, later versions of fastboot, or it can be used to replace the system image file within the xt1096-5.1-23.32-25-5_6.zip (using 7z not the built in Windows zip) to TWRP flash the full stock image.

xt1096-23.32-25-5-mofo-pkg.7z is the latest version of the rom for mofo users with SuperSU, Xposed, CF.Lumen, Better Battery Stats, and more preinstalled for mofo users.
[X 2014 Android Development] mtoomey79:
Just wanted to say thanks for this [MENTION=5849464]mikeoswego[/MENTION]
[X 2014 Android Development] bcmyspace:
Followed the instructions to the point. It works flawlessly. Thank you for your contribution.
[X 2014 Android Development] mikeoswego:
Thanks, glad its working for you!
[X 2014 Android Development] mikeoswego:
Thanks for the feedback!
[X 2014 Android Development] jrbmed08:
Hi Mike, I have a question that isn't related to this ROM but since you've been so knowledgeable and helpful about the XT1096 in general, hopefully you can help. I sold my Moto X after using it on Cricket for a month or so on a CM13-based ROM (crdroid). The buyer rolled back to lollipop and is now having trouble getting a data connection on Verizon. We tried adjusting the APN settings to no avail. He found out that it was somehow still on Cricket PRL files. Do you know of any way to get Verizon prls back onto it? For example, would flashing completely back to stock do anything? I'm not very familiar with what prl files do and didn't even know what they were before this issue came up. Thanks for any help you can give me!
[X 2014 Android Development] mikeoswego:
Getting updated PRL's was the main reason to dial *228 in the old days. PRL is Preferred Roaming List and defines which towers a phone can connect to.

On phones with LTE, the PRL is controlled by the SIM card and dialing *228 isn't allowed. The phone gets the current PRLs when it first connects to the network and future updates are scheduled by Verizon.

I've heard that powering down the phone, removing the SIM and powering it up without the SIM, waiting until the phone complains about the missing sim, then powering down, reinstalling the SIM and powering up might fix it.

I presume the buyer did a factory reset or at least wiped Data before going back to Lollipop (CM12 or stock?); doubt it would have worked without that anyway.

He could try claiming that his dog ate the SIM card to get Verizon to send him a new one to try.

And if nothing else a restore to the full stock rom with a factory reset from the stock recovery might be the ticket as a last resort.
[X 2014 Android Development] jrbmed08:
Thank you so much! I passed your suggestions along and hopefully it will be an easy fix.
[X 2014 Android Development] zkrocek:
I just wanted to pop in to say that this guide was not only what I needed, but it was simple and easy to understand. What a perfect guide for anyone in this situation. Follow it to the T and you'll have no issues.

Thanks again!
[X 2014 Android Development] locusto03:
After following the instructions explicitly, booting into Android for the first time, and completing the initial Setup Wizard, I keep getting the error "Unfortunately, Setup Wizard has stopped." After going through the process a second time and seeing the error again (this time opting to enter a Google account instead of skipping that part), a notification appeared regarding Play Store updates. After tapping on the notification and installing Nova Launcher via Play Store, everything seems to be working fine now. It seems the error was caused by not having a launcher. Anybody else have this problem? I used the pico version of Open GApps, btw.

And thanks to mikeoswego for the great work!
[X 2014 Android Development] mikeoswego:
Do you have a .gapps-config or .gapps-config.txt file in the same place as your OpenGApps zip file?

The rom has the Google Now launcher (and the required Google Search for the launcher to work) like was included by Motorola. If you go to Settings -> Home, is the Google Now launcher listed as an option? It would be possible for keywords in a .gapps-config file to delete the default launcher leaving you with no launcher which would cause the problem you saw. It would be great if you would post your open_gapps_debug_logs.tar.gz file that was created in the same place as the OpenGApps zip flle.
[X 2014 Android Development] locusto03:
Nope, I didn't use a .gapps-config for this install. I double-checked and do not see a config file present. I've since realized there was neither Chrome nor the AOSP browser after the install. Perhaps .gapps-config is required to exclude the launcher, etc. from removal? I'll PM you regarding the gapps debug logs (not sure if it includes any identifying information). Thank you.
[X 2014 Android Development] mikeoswego:
In your first post, you said there was no launcher, did you mean there was no browser as you're saying in this post?

I'm uploading an updated version that is going to change this but there has been no browser in any of the TWRP flashable versions of this ROM. Since it is not an AOSP ROM, it never had the AOSP browser and Chrome was the browser installed by Motorola. The OpenGApps installer does not install Chrome until the Full level and higher so that is a potential problem. I'm going to leave Chrome in the ROM so those installing a smaller version of the GApps will still have a browser. For the same reasons, I'm going to stop removing Google Text-To-Speech from the ROM since that is required for Google Now and probably Moto Voice to work.

I noticed some inconsistencies in the OpenGApps log files that you uploaded. It says you flashed the Stagefright patch, then the xt1096-5.1-23.32-25-5_6.zip ROM file. The OpenGApps installer zip was flashed next, but OpenGApps says the version of the ROM it found was OmniROM-4.4.4-20160206-victara-HOMEMADE where it should have just said "n/a" in the log. I'm not sure where that text could have come from, it definitely didn't come from the ROM in this thread. I've added a string to build.prop so in the future something informative will be shown instead of n/a for ROM Version in the OpenGApps log.

The comments above are just some observations. I think you are up and running now and I'm updating the ROM based on these (potential) problems.
[X 2014 Android Development] mikeoswego:
xt1096-5.1-23.32-25-5_7.zip

I've uploaded an updated version of the factory based rom. Chrome and GoogleTTS are no longer removed from the rom so those using a smaller GApps package will not be left without a browser or Text-To-Speech capability.

SuperSU v2.65 and Xposed v80 are included in this update.

There is little/no reason to update if things are working for you. The updates to SuperSU and Xposed are fairly minor, if you want those updates without flashing the entire ROM, you can use the installer zips for SuperSU and Xposed to update your existing install.

Latest ROM: xt1096-5.1-23.32-25-5_7.zip

Latest SuperSU: SuperSU v2.65

Latest Xposed Framework: Xposed v80
[X 2014 Android Development] locusto03:
I originally meant there was no launcher. I later realized there was also no browser, which is actually not a big deal as one can easily install one via the Play Store. I just wasn't sure if it was relevant to the missing launcher. In the Play Store, the Google Now Launcher does not show as installed. After installing Nova Launcher, I pressed the nav bar home key, and there was not the usual prompt to select a launcher to complete the action with.

The OmniROM entry is strange, as I flashed the files in this thread immediately after unlocking the bootloader.

I'm not sure what went wrong, but things are working now. Thank you for the feedback.
[X 2014 Android Development] enchilader:
Anybody having issues with Snapchat login? I just installed the ROM, haven't done anything to it, and Snapchat is giving me the "Temporarily failed login" error.
[X 2014 Android Development] tyleras3:
Snapchat won't log in you with Xposed installed unfortunately. I got around it by having Snapchat backed up with TiBu before flashing this ROM, and then I just restored data so I was already logged in. Otherwise, you can uninstall Xposed, sign in to Snapchat, then reinstall it.
[X 2014 Android Development] enchilader:
Yea I meant to post on this thread after solving the issue but forgot about it. Uninstalling Xposed worked for me.
[X 2014 Android Development] scififan2715:
Is there a way to reinstall exposed after logging in without reinstalling the rom?
[X 2014 Android Development] drewski_1:
Just flash Xposed zip from the official thread. I "upgraded" to Xposed v80 like that

Sent from my Moto X
[X 2014 Android Development] mikeoswego:
The thread is here: http://xdaforums.com/showthread.php?t=3034811

Use the sdk22-arm version of Xposed:	xposed-v80-sdk22-arm.zip
[X 2014 Android Development] faXal@21:
I can se these debloat scripts on other 5.x roms.

I want to debloat my stock rom that is official flash through fastboot mode..

se/use :)
[X 2014 Android Development] mikeoswego:
The debloat scripts are mostly made to remove the Verizon bloat that is installed on the xt1096. There shouldn't be any problem running the zips on some other variant but they may not do anything. Make a backup first and then if something does go wrong, you can restore the backup. There are 2 different debloat zips, the one that has keepconnect in the name does not remove things that you need to use not only Moto Connect but the Motorola gallery highlight reel music download and a few other things like that.

In addition to what the flashable zips remove, I also removed the following folders in the base xt1096 rom:

/system/priv-app/Avatar

/system/app/AvatarPermissionsApp

/system/app/Bug2GoStub

/system/priv-app/com.customermobile.preload.vzw

/system/priv-app/DemoMode

/system/priv-app/fswriter

/system/priv-app/GuideMe

/system/app/LMIRescue

/system/priv-app/LMIRescueSecurity

/system/priv-app/LocalWipePolicyManager

/system/app/MediaShortcuts

/system/priv-app/MotoCare

/system/priv-app/MotoCareInt

/system/priv-app/VerizonSSOEngine

/system/priv-app/VMobileSecurity

/system/priv-app/VzwAVS

/system/app/vznavigator

Its documented in the first post what each of these items are, I have always removed these from the first version of this rom. You can use your root file explorer to remove these items.