yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
[MENTION=2576071]Haxxa[/MENTION] is correct in what he says.

I like the CM roms and my go there at some point in time, I've run them on all my previous phones. Keep in mind that the active display feature, Moto shake features, etc don't work with the CM rom. So do make a TWRP backup of /system and /data so that you can go back easily if you don't like CM when it is available for the XT1096.
[X 2014 Android Development] JulesJam:
The XT1095 runs different radios from the XT1096. You can't just flash a custom ROM meant for the XT1095 onto the XT1096. The AT&T XT1097 can b/c that device is identical hardware-wise to the XT1095. The XT1096 has different hardware from the XT1095.

The XT1096 has both a CDMA and an LTE radio. The XT1095 does not have the CDMA radio.
[X 2014 Android Development] Haxxa:
It's pretty crazy how development has all changed, yesterday it was all about figuring out how to work around a read-only system, today how to reverse all that to approach a standard solution.
[X 2014 Android Development] intx:
So I 100% understand the differences between the two radios and the fact the XT1096 is the only one with CDMA bands.

HOWEVER, if I'm using my XT1096 on T-Mobile, would I be able to flash a ROM and get on fine? That's what I'm curious about.
[X 2014 Android Development] mikeoswego:
To run the CM rom, you will have to wipe your system. Your setup that is stored in /data is not compatible. So with TWRP make a backup to your SD Card (internal memory) or OTG drive of boot, system and data. Then wipe /data, /system, /cache, /dalvik-cache. Then install the CM rom zip and give it a try. If it doesn't work, you can go back into TWRP, do the wipes again and then restore the backup you made of boot, system and data and you'll be back to where your were.

That is probably the single greatest thing about a custom recovery like TWRP; the ability to make perfect full backups allowing you to experiment without fear. In the past, I've had backups of 3 different rom setups and would switch between them depending on my mood.
[X 2014 Android Development] JulesJam:
OK well if you 100% understand it then you know you would have to flash the XT1095 NON-HLOS.bin and fsg.mbn and see what happens when you run an XT1095 ROM and kernel and put a TMobile SIM card in the phone.

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

The XT1095 and XT1096 have different hardware. Until someone does the above, we don't know how it will work. Motorola engineers do but I am not a Motorola engineer. You are going to need to convert your XT1096 to the XT1095 firmware. I wouldn't mess with the bootloader or partition table though. I believe they are the same b/t the devices but best not to flash those.

---------- Post added at 06:21 PM ---------- Previous post was at 06:18 PM ----------

I think he needs to flash the XT1095 modem and baseband too. I would just make a nandroid and then flash all of the XT1095 firmware except leave the bootloader and partition table alone. Then pop a TMobile SIM card in the device and see how it works.

If the phone works, then he could use the XT1095 custom ROMs.

I would try it myself but I shattered my MX14 screen 2 days before the bootloader unlock and so it is not worth it to me to pay to unlock it since I will have to make an accidental damage claim and get a refurb.
[X 2014 Android Development] redwings73:
Flawless, so far! Thanks, Mike!
[X 2014 Android Development] mikeoswego:
Yes, I'm sure you're right about the need to flash the other modem software, etc.
[X 2014 Android Development] JulesJam:
When I was testing out MoFo, I flashed both the AT&T and XT1095's system images to my phone and they booted but my phone would not work as a phone. Obviously since MoFo only flashes unsigned files to system and my bootloader is locked, I couldn't flash the AT&T or XT1095 radios to test this out. I know the hardware is different b/c on another thread we compared the pics of the hardware submitted to the FCC for both the XT1096 and XT1095 and there were detectable hardware differences b/t the boards.
[X 2014 Android Development] IonMushroom:
Previously was running the v2 build since its release and just flashed to 3.1F; is anyone else having charging issues?

In particular my phone is reporting a crazy ETA for when the phone will be fully charged. (As well as it actually charging slow).

I dont have specifics on v2 but previously charge times werent any more than 1hr +/- half an hour from 15%. (Doubt its the charge method).

Right now i'm getting 2 Hours ETA at 70%.
[X 2014 Android Development] mikeoswego:
Did you clear the dalvik cache?
[X 2014 Android Development] GatorsUF:
Is there any way to make your img into a flashable zip for TWRP mike? It would be nice to have them on my SD card for when I am not near a computer.

P.S. can you tell me how to unlock tethering? I am on the stock 5.1 firmware with TWRP and bootloader unlock, so in theory I should be able to modify my system to do it right?
[X 2014 Android Development] drewski_1:
TWRP Q - see post #669.
[X 2014 Android Development] GatorsUF:
Ah thanks, I actually read that post but I skipped that last part. Looking forward to the flashable zip.
[X 2014 Android Development] mikeoswego:
To enable tethering edit /system/build.prop and add "net.tethering.noprovisioning=true" (without the quotes) to the end of the file. Reboot for the change to take effect.

I've worked some more with the TWRP flashable image but have been sidetracked by something else. But what you can do is make a TWRP backup of /system to your sdcard and restore that to get the same effect as flashing the image.
[X 2014 Android Development] IonMushroom:
prior to flashing? Yes.

Same process as when I originally brought it up to 5.1 used root browser and manually deleted both /data/dalvik-cache and /cache

---------- Post added at 01:13 PM ---------- Previous post was at 01:07 PM ----------

also just now wiped cache from recovery.

Still getting a 3HR estimate from 40%.

---------- Post added at 01:23 PM ---------- Previous post was at 01:13 PM ----------
[X 2014 Android Development] mikeoswego:
TWRP based stock xt1096 v5.1 ROM

I've created a base XT1096 v5.1 stock based image that is setup like a custom ROM. This image has tether enabled in build.prop, Busybox and SQLite3 are installed. The ROM has been rooted with SuperSU. Support for DNS in Busybox is included. Certain apps that are potentially spyware or are outdated have been removed. Even more stock apps can be removed via TWRP with the xt1096-5.1-debloat.zip file available below and in post 2. As time permits I'll create some more TWRP zip files to add Viper4Android, the stagefright patches when released, etc.

Important: This ROM, like other custom ROMs, does not included GApps (like PlayStore, etc.) Most everyone will want to download a GApps package and include it in the list of zips to install in TWRP. There are several GApps packages out there, TK GApps are very flexible and can be configured to install just the bare minimum or the full set of Google Apps: TK GApps 5.1

The TWRP flashable image is available here: xt1096-5.1-stock-20150819.zip

The debloat zip forTWRP is here: xt1096-5.1-debloat.zip

Files deleted from the stock image:

Avatar

AvatarPermissionsApp

Bug2GoStub

com.customermobile.preload.vzw

CQATest

DemoMode

Email

Exchange2

fswriter

GuideMe

LMIRescue

LMIRescueSecurity

LocalWipePolicyManager

MediaShortcuts

MotoCare

MotoCareInt

VerizonSSOEngine

VMobileSecurity

VzwAVS

vznavigator

Additional apps removed by the debloat zip:

3c_main

ECID_VZW_Victara

GoogleHindiIME

GooglePinyinIME

iWnnIME

KoreanIME

com.gotv.nflgamecenter.us.lite

VZMessages

3c_checkin

3c_devicemanagement

3c_notification

3c_ota

BodyGuardApp (Alerts)

Verizon Cloud

Verizon CloudSetup

Entitlement

MotorolaConnect

MyVerizon

VVM3
[X 2014 Android Development] jrbmed08:
Will flashing this through TWRP erase our data? All I know of flashing ROMs outside of Mofo comes from my old experience with the Galaxy Nexus and ClockworkMod, and it erased my data every time.
[X 2014 Android Development] Haxxa:
No - Simply don't wipe /data partition and data will remain - do note you will have to reinstall xposed and adaway however. Ensure to wipe delvik cache and cache when installing rom.
[X 2014 Android Development] afgeoff2010:
How would you go about installing xposed after you flash the rom from post#684? I tried using TWRP and it wouldn't flash because the SDK is 22 and it only uses 21 ATM.
[X 2014 Android Development] mikeoswego:
More TWRP zips and some useful links

The zips attached below are available for use with TWRP on the xt1096-5.1 image:

xt1096-5.1-debloat-keepconnect.zip - Removes the apps in the debloat list but keeps those needed for Connect

xt1096-5.1-CM-Stuff.zip - Adds CM Trebuchet and AudioFX to image (removes stock Audio Effects app)

xt1096-5.1-Viper4Android.zip - Adds Viper4Android (disables selinux security and removes Audio Effects app)

Useful Links:

Xposed Framework for Android 5.1 - v71 / 20150816 / SDK22 - Install this zip via TWRP to install the Xposed framework

Xposed for Lollipop Installer app - Download this apk and install the Xposed management app using your root file explorer

CF.lumen xda thread - Or search the Playstore fo CF.lumen

BetterBatteryStats xda thread - Get the BetterBatteryStats installer here

TWRP for Motorola Moto X 2014 - TWRP info page for MotoX 2014

TWRP for victara - TWRP download page

[GAPPS][5.1.x] Up-to-Date GOOGLE APPS (TK GApps) - TK GApps

AdAway xda thread - Get AdAway from here
[X 2014 Android Development] mikeoswego:
We posted at the same time, see the post after yours!
[X 2014 Android Development] afgeoff2010:
Nice!!!! Thanks again for all of you hard work.
[X 2014 Android Development] mikeoswego:
iOS Emoji font

Here is a zip for TWRP that installs the iOS Emoji font in place of the stock font:

xt1096-5.1-iOS-Emoji.zip
[X 2014 Android Development] sonic1675:
Is it safe to flash these on the 5.1h img? (not the zip, the actual img you posted earlier)
[X 2014 Android Development] mikeoswego:
The zips aren't really designed for 5.1h but some will work with it. Make a TWRP backup before using them. None of the ones I've posted are really relevant for 5.1h since it has both Viper4Android and stock audio effects, both stock and iOS Emojis, and can have CF.lumen enabled or disabled. The debloat zips would work fine. The zips to add CM stuff or Viper4Android are not compatible (and any future upgrade to Viper will break the script to switch back and forth.) Future zips for new versions of the Xposed framework, SuperSU, etc. should work fine with 5.1h. The upgrade to patch the Stagefright security issues will break the script that switches CF.lumen enabled/disabled (unless extra steps are taken.)

If you have unlocked your bootloader with Sunshine, I would recommend that you first make a backup in TWRP of /boot, /system, and /data. Then, no matter what, you can get back to where you were at that point. Then, do the following to get your phone updated to the new style images without losing your setup.

Put the new xt1096-5.1-clean-stock.zip, one of the debloat zips if you want, the Xposed v71 zip if desired, GApps zip and if you want the CM and/or Viper4Android zip in a folder on your sdcard or USB-OTG drive.

Then, go into Advanced Wipe in TWRP and select system and dalvik-cache and erase them. Then select all of the zips above in the order listed (xt1096-5.1-clean-stock.zip must be first) and flash them. When you reboot, your settings and everything will still be in place. If not, restore the backup you made. If you want Xposed, download the apk from the link in the earlier post and install it using your root file manager like ES File Explorer. Install CF.lumen from the Playstore if desired. Install AdAway from the link in the earlier post if desired.
[X 2014 Android Development] joshnat:
Unlocked the BL, installed TWRP and dirty flashed the 5.1 base zip, along with the debloat with connect, Gapps, xposed, emojis, supersu (just to be safe) and the CM stuff. Cleared cache after flashing and upon boot getting several FC's on various apps. Cleared data on those, but FC's continued. Uninstalled and reinstalled and still getting FC's. Some of the apps: Amazon, Google Play Newsstand, Xposed (UI), USAA.

Any ideas? Should I have formatted /system before flashing?

Edit: tried formatting system and flashing in a different order but results are the same. Going back to my TWRP backup until I can sort this out.
[X 2014 Android Development] Pizzuto:
Same issue, have the "f" image installed, cleared data, cache, system, dalvik, etc, factory date reset. Installed 5.1base.zip and tk5.1gappsmini.zip, wiped cache and dalvik, reboot. Everything works as normal, untill i get to the skip Email screen, then it force closes gapps services, and phone returns to select email screen! I had no issue installing this on my wife's xt1096, but she was on the last mofo image "3.1H" with +rw. My next thing to try is to mofo flash 3.1h first then try to see if installing the zip via twrp works!, but this shouldnt have anything to do with it in my opinion!
[X 2014 Android Development] amd_h4x0r:
I was running 3.1h-de and I did not run into any issues flashing via TWRP. I wiped /system and /dalvik-cache, then flashed xt1096-5.1-clean-stock.zip, xt1096-5.1-debloat.zip, xposed-v71-sdk22-arm-by-romracer-20150816.zip, and tk_gapps-modular-micro-5.1.1-20150816-signed.zip. A couple of my apps were gone (like Google Photos, Google Keyboard, etc.) but that was due to the gapps package I chose.
[X 2014 Android Development] mikeoswego:
Usually the FC's are caused by not wiping the dalvik-cache which is an option in TWRP. You need to do this when versions change or if you go back in versions on an app but that is not the case with the current ROM image. I see that I didn't update the Moto apps in this rom so your data stores for those apps won't be right until you've dl'd the new versions from the PlayStore. This would not affect Amazon, USAA, etc.

Just to be clear, you flashed the clean-stock.zip then the debloat-keep connect zip, then the correct version of the Xposed Framework from the link I posted earlier, the emoji zip and GApps. You don't need to reflash SuperSU but if you do make sure it is the 2.49 version and not 2.46; as long as you use 2.49, it shouldn't cause a problem. That version of SuperSU is here: SuperSU v2.49

Another thing you can try, since you have a backup, is to wipe both system and data in TWRP, flash everything clean just to see if that works.

BTW, I'm getting ready to upload a new version of the stock image that fixes addon.d but that has no effect on the problem you are having.
[X 2014 Android Development] mikeoswego:
You are the second one to mention a 5.1base.zip file. Which file are you referring to?
[X 2014 Android Development] Pizzuto:
You have made only 1 flashable zip to date, its called XT1096-5.1-clean-stock.zip

"im pretty sure its related to the Image I came from, as I mentioned in my previous post, it worked fine on the other mofo image with +rw on my wifes phone."
[X 2014 Android Development] mikeoswego:
Ok, unlike Joshnat, you have wiped data, a clean install, which means that nothing is left of whatever rom image you had installed before. I've tried multiple variations of a clean install including applying the full debloat zip and not installing any GApps which should be a worst case scenario. In that case, the phone booted fine, never asked for an email address. When I tried to setup a Gmail account, the phone wanted to download Play services but that failed because I didnt' install the core Google services with a GApps package.

I'd suspect that something is going wrong with the GApps install since the phone won't ask for an email without them being installed. Are you using the same TK mini GApps on both phones? Are you using a gapps-config file on either of them and is it the same? Can you look at the GApps install log that was created in the same location as your GApps zip file to see if there are any clues?
[X 2014 Android Development] mikeoswego:
xt1096-5.1-stock-20150820.zip

I've made an updated stock image file with a couple minor changes.

First, the Motorola rom was never designed to have updates or be reflashed with varying options and did not have support for addon.d scripts. I've enabled that and addon.d works correctly now. (The addon.d scripts are designed to backup certain things when you flash a rom which wipes system and anything stored there. By default, there is an addon.d script that will backup your hosts and resolv.conf file and restore them after flashing the rom. TK Gapps also creates an addon.d script that backs up all the installed GApps and restores them after you flash so it is not necessary to run the GApps installer zip again if you reflash the rom image, unless you have wiped system. If you don't want the addon.d scripts to run when flashing, simply wipe system before flashing the rom image.)

There was a typo in the resolv.conf file that will only affect those who use shell commands that need DNS like nslookup, traceroute, etc.

I'll update the debloat and other zips with addon.d functionality soon.

The new stock image is here: xt1096-5.1-stock-20150820.zip This version fixes the problem with installing Mini GApps.

Don't forget that if you do a clean flash (wipe data), it takes 4-5 minutes for the phone to start the first time.
[X 2014 Android Development] Haxxa:
Can old (last) debloat zip be used for now?
[X 2014 Android Development] mikeoswego:
Yes it will work fine. All the update zips can be applied to 20150819 and to the upcoming 20150820 that includes the latest versions of the Moto and Verizon apps in the image (many of which are deleted by the debloat zip anyway.)
[X 2014 Android Development] tacosrdelicioso:
So I have flashed this twice. Get to the setup screen and then I get to skip the tap to setup Google thing then google play services fails and I can't get anywhere. I flashed tk modular mini gapps with the rom..
[X 2014 Android Development] Pizzuto:
Same exact issue I had, see page before. What image did you come from? Tkgapps kept leaving a log, however it was corrupt and I could not read it. It seems to work if you flash the LAST MOFO image that has +rw (h image i believe) then install the new .zip from twrp!
[X 2014 Android Development] tacosrdelicioso:
idk. maybe it was d. don't know for sure. wasn't the latest though. downloading h now to test
[X 2014 Android Development] tacosrdelicioso:
So I mofo'd h to test for fun and then flashed the new rom the same way to test and got the same results. So I downloaded the tkgapps stock set and now it is work. Stupid gapps
[X 2014 Android Development] mikeoswego:
Ok, I've worked and worked with this and am able to replicate the problem when using the mini gapps. If you use the stock gapps everything works fine. (The problem occurs with the stock gapps file set to install as mini as well.)

I'm not sure if there is something missing in the rom that I can add or if it is a problem with the gapps package. I'll post there for some help.
[X 2014 Android Development] mulletcutter:
So what did you do in order to get this past setup? Stock gapps?
[X 2014 Android Development] joshnat:
OK, I was using SuperSU 2.46, so I'll try that, and I'll try a clean flash, formatting /data as well. I did clear the dalvik cache both when I dirty flashed and when I formatted /system. The Gapps I was using was the mini package. Do you think that impacts this problem? I will also use the newer flashable zip of the clean rom.
[X 2014 Android Development] tacosrdelicioso:
Yup I used the tk stock gapps package and it worked
[X 2014 Android Development] tacosrdelicioso:
Nice! Stupid little things try to ruin everything
[X 2014 Android Development] joshnat:
Fantastic, thanks. Did your upload fail?
[X 2014 Android Development] betarepeating:
yeah, 404's for me. Assuming he is working on it.
[X 2014 Android Development] joshnat:
He is unstoppable!
[X 2014 Android Development] mikeoswego:
Mini GApps problem fixed

This problem is fixed with the version I've just uploaded. The problem was that the webview app used by the Motorola ROM had a naming conflict with the TK GApps setup and was being deleted and only reinstalled if the stock GApps package was being installed. I also discovered a similar problem with the keyboard and replaced it with the AOSP keyboard from the CM 12.1 rom. If you want the Google keyboard, either use the stock GApps or the Google keyboard add-on for the other TK GApps packages

The missing webview app caused the failure of the Google setup and would affect any program that used webview, I wouldn't be surprised at all if apps like Amazon, etc. needed that to work.

Here is the new version: xt1096-5.1-stock-20150820.zip

Don't forget that if you do a clean flash (wipe data), it takes 4-5 minutes for the phone to start the first time.
[X 2014 Android Development] mikeoswego:
You guys are right on top of things! It was a PEBCAK problem.. :p
[X 2014 Android Development] betarepeating:
Worked great for me. I spent a little bit of time reading to figure everything out so I thought I would post a (mini) noob guide in the style of Jules' root guide for mofo which helped me earlier:

Starting with 5.1 Mofo Rooted image provided in this thread:

First install/run sunshine. This process was painless and easy and I'm not going to waste my time typing instructions here.

Nuke the "Warning Message" boot logo

Instructions | Download

Just opened that folder and typed:

fastboot flash logo logo.bin

Installing TWRP

Instructions | Download

then do

adb reboot bootloader

fastboot flash recovery twrp.img

fastboot reboot

Now when you boot to recovery you will see TWRP!

Installing Apps

===============

Boot into recovery (TWRP)

Made backups of /system and /boot (didnt backup /data because I don't have an OTG cable or room on my internal storage - but you should!)

Copied backups to my PC

Copied the following to the TWRP folder on my phone (could put them anywhere doesnt matter):

xt1096-5.1-stock-20150820.zip

xt1096-5.1-debloat.zip

xt1096-5.1-CM-Stuff.zip

tk_gapps-modular-mini-5.1.1-20150816-signed.zip

xposed-v71-sdk22-arm-by-romracer-20150816.zip

Links to download are in the second post of this thread

Went into Wipe > Advanced Wipe and checked system and dvalik-cache and wiped them.

Installed all the zips from above in the listed order (all that matters is the xt1096-5.1-stock-20150820.zip goes first)

Rebooted

Phone sat and optimized for a long time

While waiting I downloaded:

XposedInstaller

AdAway

CF.Lumen

Dropped the APKs onto my phone once it was booted and ran them from file explorer.

Done.

Not trying to clutter up the thread or anything, but it might help someone be more confident in the upgrade from temproot -> full root :D

Thanks again for all your hard work!
[X 2014 Android Development] mikeoswego:
That's very nice, if you don't mind I'll steal that and put in the first post!
[X 2014 Android Development] betarepeating:
thanks! feel free to steal/modify/destroy/change at will without credit. Most of that is just copy pasted from the respective instructions anyways.
[X 2014 Android Development] joshnat:
Problem solved. Thanks again Mike!
[X 2014 Android Development] Aroch925:
Curiosity question. What kind of Screen On Time are you guys getting? I'm barely getting 2 hours and I feel like that's low
[X 2014 Android Development] stay-down:
I couldnt quite find the answer through search so forgive me if its in here somewhere......I may be selling my Moto X to get some funds for the 3rd Gen...anyway, the guy who wants mine still wants it rooted. Does performing a factory reset through settings allow phone to stay rooted and just start fresh and keep root in the process?? Im still on one of the 1st 5.0 IMG's that was release as it works great for me, I havent flashed anything up to 5.1 (if that matters)
[X 2014 Android Development] mikeoswego:
I don't have any data to share on that topic but wouldn't be surprised by that kind of time.