I'm looking for some guidance with an issue I am having. It seems to affect all of the XT1225/XT1254 CM 12.1 and 13 roms I have tried. I can text without issue, however, I cannot send picture (MMS) messages with either the CM messaging app, google messenger, or hangouts. Whenever a picture is attached I get back a message stating the destination is invalid. I have an XT1250 and am running on Cellcom. If I go back to my stock backup everything works fine. Does anyone have any thoughts or suggestions?
[Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL][EOL] CyanogenMod 12.1
- Thread starter Skrilax_CZ
- Start date
Try flashing the XT1250 radio from this new 5.0.2 release, after flashing CM12.1.
Last edited:
F**k just unlocked and installed CM12.1 on my XT1250..
Is there a way to relock and getting the OTA upgrade?
Is there a way to relock and getting the OTA upgrade?
Once you find it and download it, you can flash it manually. However, you will be downgrading from custom Lollipop 5.1.1 ROM (with lots of tweaks) to stock 5.0.2.
On the XT1225, we had stock 5.0.2 since April 2015, almost a year ago. It was VERY laggy. Maybe Motorola has fixed it for the XT1250? I don't know. I was so glad to go to CM custom ROM, first 12.0 (Lollipop 5.1) and then CM12.1 (Lollipop 5.1.1).
For XT1250 people who have not unlocked their bootloaders, stock 5.0.2 is the best they'll have (upgrade from 4.4.4), whereas those running custom ROMs already have even more advanced software -- 5.1.1 and even Marshmallow -- thanks to CM dev @Skrilax_CZ.
But if you still want it, I'm sure @baybutcher27 will eventually add it to his collection of stock images. It just rolled out. I can't find a download link yet.
In my thread below, he posted a link to his folder where he keeps all the Quark stock images. I had only mirrored factory stock images for Mexico, Puerto Rico, India, Brazil, plus some TWRP backups I made. But @baybutcher27 keeps an online folder with EVERY Quark stock image, including for the XT1250, and posted that link in my thread.
Stock 5.0.2 for the XT1250 is not there yet -- only 4.4.4 -- but probably will be soon?
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
http://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
Last edited:
I have flashed brasil 5.0.2 radio (only radio) into Verizon XT1254 running Android 5.1 and now I dont have network, and bootloader and firmware doesnt show Baseband version. I flashing radio but everything remains the same.
Thanks for the suggestion, but no luck. I did the OTA update for 5.0.2, but I still get the same issue. Still says, "INVALID DESTINATION ADDRESS" for MMS messages. Everything else works fine. MMS is working fine with the stock 5.0.2 update. This has to be an issue with how the CM ROM is handling MMS. Strange and frustrating.
Heads up, there's a Quark-specific change coming to the next 12.1 (Lollipop) nightly:
http://www.cmxlog.com/12.1/quark/
http://www.cmxlog.com/12.1/quark/
The battery drain is crazy bad with BHB27-128 and latest nightly.
Last edited:
When you say latest nightly, what date? The last two at the time I'm writing this are 3/23 and 3/24, and we don't know what you are on.The battery drain is crazy bad with BHB27-128 and latest nightly.
For me, 3/23 has been fine.
http://www.cmxlog.com/12.1/quark/
Last edited:
Did it drain that much without BH's kernel? I never experienced this with the CM kernel.The battery drain is crazy bad with BHB27-128 and latest nightly.
Sent from my DROID Turbo using Tapatalk
hi everyone
i enjoy a lot reading this forum
anyone can tell me please, how i can "unroot" my moto maxx with CM 12.1 or a way to root and unroot with a simple toggle, the reason is my Bank app
and i need root for some apps but i use that apps very rarely
thanks a lot and sorry for my english
i enjoy a lot reading this forum
anyone can tell me please, how i can "unroot" my moto maxx with CM 12.1 or a way to root and unroot with a simple toggle, the reason is my Bank app
and i need root for some apps but i use that apps very rarely
thanks a lot and sorry for my english
[2016-04-04][Moto MAXX XT1225 / Droid Turbo XT1254][PREVIEW] CyanogenMod 13.0
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-droid-turbo-xt1254-t3315912
It was March 2015 (about 4-5 months after Droid Turbo and Moto Maxx were released) when we got CM12 (Lollipop 5.0.2) BEFORE Motorola gave it to us. It was our first custom ROM for Quark.
As a result of that, other custom ROMs became available over the past year to our Quarks (Nexus Experience, Resurrection Remix, Sony Xperia, Mokee) -- some CM-based and others more pure AOSP. But ALL were a direct result of @Skrilax_CZ work, because of the Quark custom kernel he coded for us to first work with CM ROM. ALL those other ROMs (even non-CM) used his kernel.
@baybutcher27 came along and developed a custom kernel BHB27 -- which I use with CM12.1 -- but even it is based on @Skrilax_CZ kernel work. I appreciate @baybutcher27's work on the kernel, as well as bringing us official TWRP recovery, and all the others who brought us ROMs over the past year.
But we can never thank @Skrilax_CZ enough for his efforts. Without him (his CM ROM work, but especially his kernel work), our Quarks probably would not have any custom ROMs whatsoever. Until he came along, I was forced to use rooted stock 4.4.4 with Xposed/Gravity Box to emulate a custom ROM.
Yes, Motorola will eventually release a Marshmallow stock ROM. But thanks to @Skrilax_CZ, we have choices and do not have to wait for Motorola.
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-droid-turbo-xt1254-t3315912
With CM13 (Marshmallow) about to go nightly and CM12.1 (Lollipop) about to go End of Life, just wanted to say thanks again to @Skrilax_CZ for his efforts over the past year.
It was March 2015 (about 4-5 months after Droid Turbo and Moto Maxx were released) when we got CM12 (Lollipop 5.0.2) BEFORE Motorola gave it to us. It was our first custom ROM for Quark.
As a result of that, other custom ROMs became available over the past year to our Quarks (Nexus Experience, Resurrection Remix, Sony Xperia, Mokee) -- some CM-based and others more pure AOSP. But ALL were a direct result of @Skrilax_CZ work, because of the Quark custom kernel he coded for us to first work with CM ROM. ALL those other ROMs (even non-CM) used his kernel.
@baybutcher27 came along and developed a custom kernel BHB27 -- which I use with CM12.1 -- but even it is based on @Skrilax_CZ kernel work. I appreciate @baybutcher27's work on the kernel, as well as bringing us official TWRP recovery, and all the others who brought us ROMs over the past year.
But we can never thank @Skrilax_CZ enough for his efforts. Without him (his CM ROM work, but especially his kernel work), our Quarks probably would not have any custom ROMs whatsoever. Until he came along, I was forced to use rooted stock 4.4.4 with Xposed/Gravity Box to emulate a custom ROM.
- We got CM12 Lollipop 5.02-based ROM before Motorola released it to Quark.
- We got CM12.1 Lollipop 5.1.1-based ROM which Motorola NEVER released for Quark.
- Now, we have CM13 Marshmallow-based ROM (plus Resurrection Remix, based on CM13 ROM).
Yes, Motorola will eventually release a Marshmallow stock ROM. But thanks to @Skrilax_CZ, we have choices and do not have to wait for Motorola.
Did you ever find a fix for this? my ro.boot.carrier = blank as well.
EDIT:
I am having the same exact issues on VZW XT1254. My getprop is
And I have tried reflashing the radios and gpt that fixed it for the other user. Any help is greatly appreciated.
Last edited:
Please ID the build you're commenting on!
Ha, comment 1254 from xt1254!
Just got my quark (xt1254) to replace a d2vzw, so thanks for all the early work here! Since this is my daily driver, knowing which build comments are about is essential. Just saying "flashed latest build" isn't all that helpful, since this thread covers months. Thanks again and looking forward to a run with quark similar to the amazing runs I had with d2vzw and og droid.
Ha, comment 1254 from xt1254!
Last edited:
That should win you some sort of prize, don't you think? [emoji1]
re: Please ID the build you're commenting on!
If you go here -- to the CM12.1 nightly list -- it says the device is no longer supported, because the dev has switched over totally to CM13 (Marshmallow) for this device.
https://www.cmxlog.com/12.1/quark/#cm-12.1-20160119-NIGHTLY-quark.zip
This was the last 12.1 (Lollipop nighty: cm-12.1-20160405-NIGHTLY-quark.zip (385.9 MB)
which can still be found here (at the link below) for a while until CM13 nightlies push it out of the "recents" list...
https://download.cyanogenmod.org/?device=quark
I'm running that 12.1 nightly on two of my phones, until I get the time to switch both over to CM13. Runs great.
@Skrilax_CZ had mentioned possibly doing one final "snapshot" (wrap up build), but with that "device not supported" error message in the 12.1 directory, probably won't happen. That last nightly is good enough.
Well, I think the last 12.1 nightly build for Quark has been produced a few days ago.
If you go here -- to the CM12.1 nightly list -- it says the device is no longer supported, because the dev has switched over totally to CM13 (Marshmallow) for this device.
https://www.cmxlog.com/12.1/quark/#cm-12.1-20160119-NIGHTLY-quark.zip
This was the last 12.1 (Lollipop nighty: cm-12.1-20160405-NIGHTLY-quark.zip (385.9 MB)
which can still be found here (at the link below) for a while until CM13 nightlies push it out of the "recents" list...
https://download.cyanogenmod.org/?device=quark
I'm running that 12.1 nightly on two of my phones, until I get the time to switch both over to CM13. Runs great.
@Skrilax_CZ had mentioned possibly doing one final "snapshot" (wrap up build), but with that "device not supported" error message in the 12.1 directory, probably won't happen. That last nightly is good enough.
Last edited:
The error message isn't relevant, it just returns that when the query to jenkins fails. I plan to do the final snapshot when I return back from China.
No deepsleep while charging...
I had flashed the last nightly of cm12.1...just noticed that phone is getting too hot almost around 43 deg C. I did some digging than came to know using cpuspy that when i place the phone idle without charging it go into deepsleep but when the phone is on charging it doesnt go into deep sleep, any fix for it or there is another problem??
I had flashed the last nightly of cm12.1...just noticed that phone is getting too hot almost around 43 deg C. I did some digging than came to know using cpuspy that when i place the phone idle without charging it go into deepsleep but when the phone is on charging it doesnt go into deep sleep, any fix for it or there is another problem??
Are you using Qi charging or USB charging when this happens? Or both?I had flashed the last nightly of cm12.1...just noticed that phone is getting too hot almost around 43 deg C. I did some digging than came to know using cpuspy that when i place the phone idle without charging it go into deepsleep but when the phone is on charging it doesnt go into deep sleep, any fix for it or there is another problem??
In Developer Options there is a choice for "Stay Awake While Charging". Do you have this on?
Currently using wall charger only.... QC 2.0 supported... No screen turns off after 30secs... I just came to know about that screen on option from you...
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone