[Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 13.0

[Jpr0930]

Anyone else not getting gifs to animate in the stock messaging app? Not a huge deal as its been like this for me since I first jumped in several months back, just curious. Or, is it shame on me for using the stock messaging app in the first place?

 

[ChazzMatt]

Hey there guy's, how you're doing? Hope you're fine.
I just got myself a Maxx and i'm looking for a custom ROM (like i always did with my android devices), and nothing better than the good old CM. So i was wondering, how is performance/battery life of this ROM compared to STOCK?

Well, with CM13 or any custom ROM for Quark you can always install BHB27 kernel to increase performance. It's based on CM kernel but more options. That kernel has extra governors and such. And there are battery saving options in @Debuffer kernel Intelli- profiles that you can run with BHB27 kernel.

I run CM for the extra user options available. Other ROMs have even more options but CM is enough for me. If it wasn't for CM dev @Skrilax_CZ, the Quark probably wouldn't have any custom ROMs or kernels as all the custom ROMs use his CM kernel. You can't have a custom ROM for a device without a kernel. While you can port a ROM, it still needs a device-specific kernel.

If you go over to the Kinzie (Droid Turbo 2/Moto X Force) forum -- the 2015 successor to our 2014 Quark -- they never got ANY official ROM, no custom kernels. First, the Verizon-branded Droid Turbo 2 bootloader was never unlocked. And while the sibling Moto X Force is easily unlocked and rooted, all that device got was UNOFFICIAL TWRP and an UNOFFICIAL CM12.1 -- which was last updated in February 2016. Only one outdated unofficial Lollipop ROM and no custom Marshmallow ROMs whatsoever. It's a sad situation.

No dev like @Skrilax_CZ stepped in to help them with that device, like he did with our Quark.

Over here on the Quark, what @Skrilax_CZ did was the foundation of ALL our XDA development choices. He coded CM and kernel, which caused other ROMs to appear. What a lot of people don't realize is ALL the Quark custom ROMs (Lollipop and Marshmallow) all use his CM kernel.

• Then we got official TWRP from @baybutcher27 -- taking over from the unofficial TWRP @respider had started.
• @baybutcher27 also maintains two custom Quark ROMs -- Mokee AOSP and Resurrection Remix -- in addition to his BHB27 kernel and TWRP.
• More recently @NepoRood started Bliss ROM and Android Open Kang Project ROM, which works on all Quarks.
• If that's not enough choice, @calsurferpunk mainstains an "unofficial" CM13 ROM which is a hybrid of CM13 with some Resurrection Remix features.
• @iiWoodstocK has a "stock"-based Motorola Marshallow ROM that is TWRP-flashable, which works on ALL Quarks -- XT1254, XT1225, XT1250, and uses the BHB27 kernel (which of course is based on @Skrilax_CZ work).

And these are just the Marshmallow options! I haven't even mentioned the Lolllipop ROMs that still work, if for some reason you wanted them. (I'm still running CM12.1 Lolllipop on both my phone and my wife's phone.)

So, while it's easy for people to forget about CM when other snazzy ROMs come along, for our Quark they are all built on the foundation of what @Skrilax_CZ started and still maintains. He first got CM12 Lollipop working with Motorola Kitkat kernel sources (before Motorola gave us Lollipop), then CM12.1 with full Lollipop kernel, then got CM13 Marshmallow ROM working with Lollipop kernel sources (MONTHS before Motorola released Marshmallow for any Quarks), then coded a CM13 Marshmallow kernel.

 

[NepoRood]

@ChazzMatt

I agree 100%, without Skrilax_CZ, there'd be no custom ROMs for our quarks. BHB27 has been the most help to me though, and I wouldn't have been able to build anything without his guidance (but he got his from Skrilax_CZ )

 

[kingersj1]

But can we bribe him to continue with his great work for when source code is released for Android 7.0? Would love to see official CM 14!

 

[NepoRood]

But can we bribe him to continue with his great work for when source code is released for Android 7.0? Would love to see official CM 14!

I'm pretty sure he will, and BHB27 too, they know WAY more about this stuff than I do, lol

I "donated" what I could at the time to BHB27, because of his hard work on RR, which led me to building Bliss and AOKP. Bliss 7 will probably be the last in line for quark, but I'll get it up and running :good:

 

[mathk]

I checked both this forum and the verizon droid turbo forum plus the Google for the radio issues I can't ensure. I planned to flash the xt1225 radio to my xt1254.
If I do so ,can i get the band 5 and 17 unlocked? I don't need the band 13.
Secondly, do I need to force the radio manually every time I reboot?
Additionally, can I just flash the radio.img but not the bootloader?

Sent from my XT1254 using XDA-Developers mobile app

 

[ChazzMatt]

LTE bands 5 and 17 on the XT1254

I checked both this forum and the verizon droid turbo forum plus the Google for the radio issues I can't ensure. I planned to flash the xt1225 radio to my xt1254.
If I do so ,can i get the band 5 and 17 unlocked? I don't need the band 13.
Secondly, do I need to force the radio manually every time I reboot?
Additionally, can I just flash the radio.img but not the bootloader?

That's not going to work. The XT1225 and XT1254/XT1250 have different FCC ID. (See below). If you needed all AT&T bands you should have bought the XT1225. I own three.

Theoretically the other bands from the XT1225 could be unlocked on the XT1254 (since they all share the same hardware, including antennas), but it won't happen by just flashing the XT1225 radio over the XT1254.

This guy in China was trying:

[Radio]Enable Band 17 SMH 700Mhz LTE on Verizon XT1254 devices
http://forum.xda-developers.com/droid-turbo/help/rfnv-enable-band-17-smh-700mhz-verizon-t3426253

and this guy just yesterday:

XT1225 QCN Backup File Needed for a Test
http://forum.xda-developers.com/droid-turbo/general/xt1225-qcn-backup-file-test-t3445115

and see the LAST PAGE of this thread:
http://forum.xda-developers.com/droid-turbo/help/unlock-lte-bands-moto-maxx-t2986947/page5

The QCN file method seems promising, but needs more investigation. Also they need a QCN file from a Moto XT1225.

_____


The XT1225 and XT1254/XT1250 all share LTE bands 2, 3, 4, 7.

The XT1225 additionally has LTE band 5 and 17 (more bands used by AT&T).
___________________
FCC ID IHDT56PK2

____________________

The XT1254/XT1250 instead has LTE band 13 (Verizon LTE band), plus CDMA bands. While it does have some HSPA bands, there's not as many as in the XT1225.

FCC ID IHDT56PK1

______________________

To be clear, you cannot add more LTE bands which are not present in any of the Quarks. People have tried to add LTE band 20, which is used in Europe a lot. Can't be done.

However, theoretically you could enable the LTE bands available in the other Quarks, to have a phone with LTE bands 2, 3, 4, 5, 7, 13, 17. Something similar has worked for Samsung phones with Snapdragon chipsets, which is only why I say it's theoretically possible. Depends on if Motorola uses methods similar to Samsung in manufacturing.

I got very involved in this about a year ago, flashing/modding/researching LTE band unlocking -- but once I found I already had LTE band 5, then my goal was accomplished. You can search my posts from about a year ago, I documented everything thoroughly.

The two threads above which mention "QCN" files are more recent and seem to hold promise.

XT1225 QCN Backup File Needed for a Test

Hello guys,

I need help, comments, (or maybe a .qcn backup file) that can give me information about the possibility enabling LTE Band 5 (850mhz) on XT1254.

First,
Based on THIS THREAD on Verizon LG G3 VS985, some people are able to enable LTE Band 5 on their device by restoring the .qcn backup file from LG G3 D850.

Second,
I see the similarity between XT1225 and XT1254, though they are different on network frequencies

What's on my mind,
Is it possible for XT1254 to get LTE Band 5 by restoring the XT1225 NV Backup file (.qcn) using QPST? I hope you guys can understand clearly what I'm trying to do here. It would be better if someone can help me integrate Band 5 to XT1254 default RFNV file. What do you think, please share your thoughts

The only problem is I believe IMEI numbers are included in the QCN file. I don't want to give my IMEI numbers to anyone. @Vortex at top said he would keep QCN files confidential, but I paid $1850 total for my three Moto XT1225, so I can't take a chance. Sorry.

 

[mathk]

used the cm13 newest nightly for a morning. the cm13 weather menu in setting is not working. others are very good. If there are more options of double tapping the home button , e.g. open call app, it would be better.

 

[mathk]

I am still a bit confused that if I update the CM13 through OTA , do I have to reflash the gapps?

 

[svprm]

I am still a bit confused that if I update the CM13 through OTA , do I have to reflash the gapps?

If you have wiped your device during update process,definitely you have to reflash the GApps again.

 

[luiz.simoes0000]

I am still a bit confused that if I update the CM13 through OTA , do I have to reflash the gapps?

If you do not wipe data, it is not necessary.

 

[evastonian]

Delete

 

[BVarella]

Stable build

Are we going to have a stable build (snapshot, not nightly) for Moto MAXX? (CM13)

 

[vinydasilveira]

Are we going to have a stable build (snapshot, not nightly) for Moto MAXX? (CM13)

I think to have a stable build, we would need at least have all the apps and basic functions available for the official CyanogenMod. For example. When I had a Moto X 2014 CM13 Nightly had support for the snapdragon camera and you could download the Moto Camera directly by playstore. It had also led notification function. The lock screen Spectrum works with any music player. Still the Moto X 2014 does not have a Snapshot. The Nexus 6 received the Snapshot even hardware that nosos quark, but the N6 has much more support and the CM13 for it is much more complete than ours. It is easier to drop the CM13 aside and start paying attention to CM14. The CM13 came too late for Quark. Let's do it differently this time.

 

[ChazzMatt]

It is easier to drop the CM13 aside and start paying attention to CM14. The CM13 came too late for Quark. Let's do it differently this time.

Well, Marshmallow was released October 14, 2015 . CM 13 preview hit this thread February 16 2016. 4 months. I thought that was pretty amazing.

@Skrilax_CZ bought a 2nd Moto Maxx XT1225 and was able to use that to develop while still using his daily phone. It was hard to develop and do your REAL work on just one phone. He thought his phone died, so he ordered a replacement and then resurrected the original phone. So, he kept both to have extra one for development purposes.

Will u develop CM14 from Moto X Style sources?

Moto X Style already has CM14?

 

[Shooting Star Max]

I don't know since when, but today I discovered I am unable to record videos. The CM camera pretends it records, but leaves no file, and Motorola Camera says it's unable to record one second after pressing the button. Of course, I've got a logcat of such event. I tried to read it, but I know nothing about this...
https://drive.google.com/open?id=0B2EFD_NTVrKgbWRwd1FSV2dpQ0U

EDIT:*Nevermind, it turned out to be a bug with BHB27's kernel, I'll post the logcat in his thread.

 

[mathk]

I just found that I can't turn on the NFC using the 20160909 and 20160910 builds. I can't ensure if this is only my problem or not. It was on to turn on in the 20160826 build.

Sent from my quark using XDA Labs

 

[LuanGuima14]

Is there any progress in CM14 to quark?

 

[Skrilax_CZ]

I usually start porting when CM14 official nightlies start. CM14 is just too unstable right now. Although since I have 2nd MAXX, I might look on it a bit earlier

 

[Cobra04]

I usually start porting when CM14 official nightlies start. CM14 is just too unstable right now. Although since I have 2nd MAXX, I might look on it a bit earlier

Nexus 6 STILL doesn't have stock Nougat so no rush.